<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ben Kutil &ndash; Product and Growth Leader</title>
    <description>Posts and Notes from Ben Kutil</description>
    <link>https://benkutil.com</link>
    <atom:link href="https://benkutil.com/feed.xml" rel="self" type="application/rss+xml"/>
    <pubDate>2026-02-03T02:50:19Z</pubDate>
    <lastBuildDate>2026-02-03T02:50:19Z</lastBuildDate>
    <generator>Eleventy 2.0.1</generator>
      <item>
        <title>Context disconnects</title>
        <description>&lt;p&gt;There’s the old maxim, “&lt;em&gt;&lt;a href=&quot;https://linguistics.stackexchange.com/questions/36873/what-is-meant-by-the-maxim-context-is-king&quot;&gt;Context is king&lt;/a&gt;&lt;/em&gt;“. It struck me that how teams navigate context changes over time. I think there’s a gravity that pulls teams towards a high context culture.&lt;/p&gt;
&lt;p&gt;As a team first forms, there’s intentional effort to communicate in a low context manner. These &lt;a href=&quot;https://en.wikipedia.org/w/index.php?title=File:Wikimania_2018_-_Communicate_effectively_-_low_context_high_context_-_dmenard.pdf&amp;amp;page=12&quot;&gt;low context&lt;/a&gt; conversations use explicit details, include relevant information in the communication, and are easier for new people to enter.&lt;/p&gt;
&lt;p&gt;As a team works together, they can shortcut communication by relying on their shared understanding of the domain. These &lt;a href=&quot;https://en.wikipedia.org/w/index.php?title=File:Wikimania_2018_-_Communicate_effectively_-_low_context_high_context_-_dmenard.pdf&amp;amp;page=13&quot;&gt;high context&lt;/a&gt; conversations uses implicit details, assumes a common understanding, and is difficult to enter without the status and history of those communicating.&lt;/p&gt;
&lt;p&gt;A simple example that I experience almost every day: &lt;em&gt;acronyms&lt;/em&gt;. A team may intentionally start by expanding all acronyms. Over time, that practice fades away, or new acronyms get created. bonding. A shared language that only people on the team know! It’s a form of team bonding or in-culture.&lt;/p&gt;
&lt;p&gt;To combat this issue, people could look to APIs. API’s structure communication into and out of a system. They represent a great model for low context communication. They have a defined structure, define explicit detail, and even include relevant information (&lt;a href=&quot;https://json-ld.org/&quot;&gt;JSON-LD&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;For people setting up or leading teams, consider the “low context” APIs you’d develop that will bring information in and out of a team. Much like system APIs, it’ll increase the use and usefulness of the team.&lt;/p&gt;
</description>
        <pubDate>2023-01-04T00:00:00Z</pubDate>
        <link>https://benkutil.com/posts/2023-01-04-context/</link>
        <guid isPermaLink="true">https://benkutil.com/posts/2023-01-04-context/</guid>
      </item>
      <item>
        <title>The stretch pants of work</title>
        <description>&lt;p&gt;I’ve arrived late to the “joggers” game. I purchased two pairs in a effort to not have to change from jeans into sweatpants when trying to work out durring the day.&lt;/p&gt;
&lt;p&gt;Since then, I can’t get out of them. I’ve given up. Super comfortable. Convient for moving around. I’ve hit a new low.&lt;/p&gt;
&lt;p&gt;The last couple of weeks at work, we’ve talked about the need for a bit higher standards when it comes to meetings and communications.&lt;/p&gt;
&lt;p&gt;As we’ve accepted lower expecatations about appearance, have we also accepted lower expectations when it comes to agendas, action items, and communicating status?&lt;/p&gt;
</description>
        <pubDate>2022-12-22T00:00:00Z</pubDate>
        <link>https://benkutil.com/posts/2022-12-22-the-stretch-pants-of-work/</link>
        <guid isPermaLink="true">https://benkutil.com/posts/2022-12-22-the-stretch-pants-of-work/</guid>
      </item>
      <item>
        <title>Order of operations</title>
        <description>&lt;p&gt;I like to think about ways to more efficiently or effectively complete my tasks. Sometimes I express this as aesthetic improvements. Like rolling my towels a certain way. Or a functional improvement. Like stacking the dishwasher so that I can put away dishes in batches.&lt;/p&gt;
&lt;p&gt;Beyond small local improvements, I like to think about optimizing the macro order of what I do. Today, I had dishes, laundry, vacuuming, and a window-sealing project. I arranged my tasks like this:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Laundry. Collect and start the first load.&lt;/li&gt;
&lt;li&gt;Dishes. Put away and re-load the dishwasher. Hand wash knives and pans.&lt;/li&gt;
&lt;li&gt;Window Sealing. Put tape around all windows.&lt;/li&gt;
&lt;li&gt;Vacuum. Vacuum while waiting for tape to set.&lt;/li&gt;
&lt;li&gt;Finish window sealing.&lt;/li&gt;
&lt;li&gt;Put away laundry.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This order allowed me to take advantage of the long cycle times of the laundry and dishwasher. It feels rewarding to work efficiently.&lt;/p&gt;
&lt;p&gt;I don’t often think about “cycle time” for tasks at work. I should try to use it as effectively at work tasks as I do with chores.&lt;/p&gt;
</description>
        <pubDate>2022-12-18T00:00:00Z</pubDate>
        <link>https://benkutil.com/posts/2022-12-18-order-of-operations/</link>
        <guid isPermaLink="true">https://benkutil.com/posts/2022-12-18-order-of-operations/</guid>
      </item>
      <item>
        <title>Debugging is hard</title>
        <description>&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; It took me another hour to debug Cloudflare Page build problems. Cloudflare stalled when referencing the package using the github short code format in &lt;code&gt;package.json&lt;/code&gt;. After trial an error, it seems using the full &lt;code&gt;https&lt;/code&gt; based git url works well enough.&lt;br /&gt;
Tonight, I spent 30 minutes trying to figure out why something wasn’t working. Found out that the package I used had an issue in its &lt;strong&gt;core functionality&lt;/strong&gt;. And it wasn’t actively maintained.&lt;br /&gt;
Thankful someone had &lt;a href=&quot;https://github.com/sentience/eleventy-xml-plugin&quot;&gt;forked and fixed&lt;/a&gt; the issue.&lt;br /&gt;
Anyways. I don’t miss this part of programming.&lt;/p&gt;
</description>
        <pubDate>2022-12-15T00:00:00Z</pubDate>
        <link>https://benkutil.com/posts/2022-12-15-debugging-is-hard/</link>
        <guid isPermaLink="true">https://benkutil.com/posts/2022-12-15-debugging-is-hard/</guid>
      </item>
      <item>
        <title>Christmas lists are boring</title>
        <description>&lt;p&gt;As an adult, kids Christmas lists are boring. It does make giving a “gift” easier. It removes all the thought and care that makes it a “gift”. Even more if you get them all from Amazon. Point, click, buy. Love Dad/Uncle Ben.&lt;br /&gt;
I think next year I’ll go rougue. No lists, only vibes and care and interest. Watch out kids.&lt;/p&gt;
</description>
        <pubDate>2022-12-14T00:00:00Z</pubDate>
        <link>https://benkutil.com/posts/2022-12-14-christmas-lists-are-boring/</link>
        <guid isPermaLink="true">https://benkutil.com/posts/2022-12-14-christmas-lists-are-boring/</guid>
      </item>
      <item>
        <title>Shipping the org chart</title>
        <description>&lt;p&gt;From a person’s point of view, we’re still “shipping the org chart” of government agencies.&lt;br /&gt;
Sure we’ve improved the experience of those online experiences. And have tried to structure them around verbs and the way people think. But people still need to find out what benefi they need. And what agency offers it.&lt;br /&gt;
It’s taken us 10 years to get consistent on creating good government websites.&lt;br /&gt;
How long will it take us to abstract the org chart of government from people’s day to day?&lt;/p&gt;
</description>
        <pubDate>2022-12-13T00:00:00Z</pubDate>
        <link>https://benkutil.com/posts/2022-12-13-gov-org-chart/</link>
        <guid isPermaLink="true">https://benkutil.com/posts/2022-12-13-gov-org-chart/</guid>
      </item>
      <item>
        <title>Hello Again</title>
        <description>&lt;p&gt;My new years resolution for 2020 was to publish more to my website. I started on &lt;a href=&quot;https://github.com/benkutil/benkutil.github.io/pull/45/files&quot;&gt;January 20th, 2020&lt;/a&gt;, and made it to &lt;a href=&quot;https://github.com/benkutil/benkutil.github.io/pull/50/files&quot;&gt;March 2nd, 2020&lt;/a&gt;. One Year later, I &lt;a href=&quot;https://2020.benkutil.com/meta/website/2021/03/02/day-1&quot;&gt;tried again&lt;/a&gt;. It’s now 2022. A lot has happened. And for better or worse, or because third time’s the charm, I’ve dusted off the old website.&lt;/p&gt;
&lt;h2 id=&quot;development-challenges&quot; tabindex=&quot;-1&quot;&gt;Development challenges &lt;a class=&quot;header-anchor&quot; href=&quot;https://benkutil.com/posts/2022-11-26-hello-again/#development-challenges&quot;&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;I haven’t professionally written code since 2017. The 2016 version of my website relied heavily on &lt;a href=&quot;https://gulpjs.com/&quot;&gt;gulp&lt;/a&gt;, &lt;a href=&quot;https://sass-lang.com/&quot;&gt;sass&lt;/a&gt;, and other popular concepts at time. In 2020, I didn’t have time for that. I spent 30 minutes at a time trying to get things done and documenting the changes I made. In 2022, my environment and interest has changed even more.&lt;/p&gt;
&lt;h3 id=&quot;goodbye-computer&quot; tabindex=&quot;-1&quot;&gt;👋 Goodbye computer &lt;a class=&quot;header-anchor&quot; href=&quot;https://benkutil.com/posts/2022-11-26-hello-again/#goodbye-computer&quot;&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;This time around, I’ve introduced a few new challenges. I no longer have a personal computer. I also no longer want to maintain a personal server.&lt;/p&gt;
&lt;p&gt;Luckily, it’s been so long since I’ve written code that GitHub has made CodeSpaces available to all accounts. &lt;strong&gt;I love CodeSpaces&lt;/strong&gt;. I didn’t realize how much I missed having access to the command line. Getting setup and writing code took no time. Writing code from the airport, tethered to my phone, and being able to re-connect seamlessly felt amazing.&lt;/p&gt;
&lt;h3 id=&quot;goodbye-personal-server&quot; tabindex=&quot;-1&quot;&gt;👋 Goodbye personal server &lt;a class=&quot;header-anchor&quot; href=&quot;https://benkutil.com/posts/2022-11-26-hello-again/#goodbye-personal-server&quot;&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;In 2016, I was looking for a new job after 8+ years of working for myself. I used it as an opportunity to manage and setup a very fast web server on Digital Ocean. That same instance has run for 6 years. Some time in year 2 or 3, I could no longer update the server, and I didn’t care enough to rebuild its configurations. I even gave up on my intricate capistrano and &lt;a href=&quot;https://github.com/benkutil/benkutil.github.io/tree/develop-2016/config/gulp&quot;&gt;gulp configs&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In an interest limit time to first bit, I had used CloudFlare as a CDN proxy to my server. Again, thanks to not having paid attention to web development for a very long time, I could now make use of &lt;a href=&quot;https://pages.cloudflare.com/&quot;&gt;CloudFlare Pages&lt;/a&gt;. I’m now using CloudFlare pages to host both of the previous websites (&lt;a href=&quot;https://2023.benkutil.com/&quot; title=&quot;Open the 2023 version of this website&quot;&gt;2023&lt;/a&gt;,&lt;a href=&quot;https://2020.benkutil.com/&quot; title=&quot;Open the 2020 version of this website&quot;&gt;2020&lt;/a&gt;,&lt;a href=&quot;https://2016.benkutil.com/&quot; title=&quot;Open the 2016 version of this website&quot;&gt;2016&lt;/a&gt;). It also builds and deploys this website.&lt;/p&gt;
&lt;h3 id=&quot;goodbye-jekyll-hello-11ty&quot; tabindex=&quot;-1&quot;&gt;👋 Goodbye Jekyll, 👋 hello 11ty. &lt;a class=&quot;header-anchor&quot; href=&quot;https://benkutil.com/posts/2022-11-26-hello-again/#goodbye-jekyll-hello-11ty&quot;&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;I feel totally confident/happy about deciding to jettison a local development environment and a personal server. I feel less confident about my decision to switch to &lt;a href=&quot;https://benkutil.com/posts/2022-11-26-hello-again/11ty.dev&quot;&gt;11ty&lt;/a&gt;. Mostly because I have to relearn a bunch of configuration commands. On the upside, I have fewer depedencies, and I’m not moving around between &lt;code&gt;ruby&lt;/code&gt; and different implementations of &lt;code&gt;javascript&lt;/code&gt; or &lt;code&gt;json&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;consistency-and-low-volume&quot; tabindex=&quot;-1&quot;&gt;Consistency, and low volume &lt;a class=&quot;header-anchor&quot; href=&quot;https://benkutil.com/posts/2022-11-26-hello-again/#consistency-and-low-volume&quot;&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Over the last couple of years, I’ve gotten serious about improving my endurance and performance on a bike. I’ve learned a lot about endurance training practices. Two concepts that I intend to transfer over are those of appropriate volume and consistency.&lt;/p&gt;
&lt;p&gt;In an endurance sport, consistency and volume represent two of the three primary factors of training that will help you progress in developing your endurance capacity. Consistency in training represents the most important factor. The volume of weekly training is important to progressing towards your goals. However, you shouldn’t pursue volume over the consistency. For example, it is better to consistently train for three days a week over a 2 month period than it is to ride 5 days a week, but inconsistently week to week, over that same time frame.&lt;/p&gt;
&lt;p&gt;Back in 2020, I had the goal of working on my website daily, for 30 minutes at a time. That was “high volume”. And it turned out hard to execute on daily.&lt;/p&gt;
&lt;p&gt;This time around, I intend to apply some of the things that I’ve learned from training to working on this website. It’s more important that I continue to work on the website year over year than it is that I work on it from day to day. Setting up a pace that enables that long term work represents something I intend to create.&lt;/p&gt;
</description>
        <pubDate>2022-11-26T00:00:00Z</pubDate>
        <link>https://benkutil.com/posts/2022-11-26-hello-again/</link>
        <guid isPermaLink="true">https://benkutil.com/posts/2022-11-26-hello-again/</guid>
      </item></channel>
</rss>