<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Noah Eisen on Medium]]></title>
        <description><![CDATA[Stories by Noah Eisen on Medium]]></description>
        <link>https://medium.com/@ncteisen?source=rss-90a527b39ea0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*r2qDsANzFvXqvXLfrHPL4Q.jpeg</url>
            <title>Stories by Noah Eisen on Medium</title>
            <link>https://medium.com/@ncteisen?source=rss-90a527b39ea0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:52:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ncteisen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[When process works like an accelerant, not a tax]]></title>
            <link>https://craft.faire.com/when-process-works-like-an-accelerant-not-a-tax-4b18deea53b0?source=rss-90a527b39ea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b18deea53b0</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[staff-engineering]]></category>
            <dc:creator><![CDATA[Noah Eisen]]></dc:creator>
            <pubDate>Tue, 27 May 2025 18:01:26 GMT</pubDate>
            <atom:updated>2025-08-07T20:48:39.289Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tips for finding the high-value, low-cost processes that give your teams rocket fuel</h4><figure><img alt="Title image for the post “When process works like an accelerant, not a tax” with illustrated gears representing Engineering." src="https://cdn-images-1.medium.com/max/1024/1*bYOmqiIir3j4LeNuNhR8RQ.jpeg" /></figure><p>By the time I became a Staff Engineer, I thought I had a solid handle on what made engineering teams work. I’d led projects, mentored junior devs, and made architectural decisions that stuck around longer than most front-end frameworks. But about a year ago, I got a crash course in a different layer of the stack: people, process, and what it really takes to keep a 10-person team running smoothly.</p><p>I stepped into the Senior Engineering Manager role for the Shipping &amp; Pricing team at <a href="https://www.faire.com/">Faire</a> during a pivotal moment. We were shipping some of the company’s top priorities while also navigating a flood of customer tickets. On any given day, we were balancing feature rollouts, experimental bets, and high-stakes support work — and I was trying to stay hands-on while figuring out what it actually meant to lead and manage.</p><p>What helped me find my footing was introducing some process. Not the bureaucratic kind that slows everyone down — but the kind that quietly makes everything run smoother.</p><h3>Good process can be rocket fuel (or a dead weight)</h3><blockquote><em>“Individuals and interactions over processes and tools.”</em></blockquote><p>It’s the first line of the <a href="https://agilemanifesto.org/">Agile Manifesto</a>, and for good reason. People — not process — are what builds great software. But I’ve also learned that the right process, at the right time, can be a force multiplier.</p><p>I used to think “process” was a dirty word. I pictured endless status calls and vague Jira templates. But when done right, process isn’t overhead — it’s leverage. It’s clarity. It’s speed.</p><p>Done wrong, though, it’s a dead weight. The key is knowing the difference — and being willing to rebuild when it stops serving the team. A good process does two things:</p><ul><li>It solves a problem</li><li>It saves more time than it costs to run</li></ul><p>Those two simple checkboxes are the litmus test. If a process costs more time and energy than the clarity it brings, it’s a net negative — a drag on productivity. And if a process is not solving a problem, it’s just confusing motion for progress.</p><p>The trick is recognizing that every process has a tradeoff: it brings structure, but also overhead. When that overhead outweighs the benefits — when a process becomes more about rituals than results — it’s time to re-evaluate.</p><p>We can break processes down by value and cost:</p><figure><img alt="A 2x2 chart mapping Value vs. Cost with quadrants: Rocket thrusters, Launchpads, Paperweights, and Dead weights, each with matching icons." src="https://cdn-images-1.medium.com/max/1024/1*mzpf8CUgEOjZmF_nrwT3lQ.png" /><figcaption>How I envision the cost-value matrix.</figcaption></figure><p><strong>Low-cost, high-value → Rocket thrusters</strong><br>Tiny bursts of effort that create outsized lift, like lightweight, high-level project trackers to maintain status and roadmap, or per-team bug rotation process tuned to exactly what the team needs.</p><p><strong>High-cost, high-value → Launchpads</strong><br>Heavy investments that become the sturdy platform for bigger leaps, such as org-wide, top-down technical OKR generation process, or incident-response processes with blameless retrospectives.</p><p><strong>Low-cost, low-value → Paperweights</strong><br>Harmless trinkets that clutter calendars more than they help, like a daily stand-up where everyone just reads their status report aloud with zero discussion, or a mandatory labeling system for all JIRAs.</p><p><strong>High-cost, low-value → Dead weights</strong><br>Bureaucratic ballast that drags velocity to a crawl. Examples of this include: a 12-step PR checklist tacked onto every merge, multi-tier approval chain for trivial copy changes in production, and daily syncs that are just long status updates.</p><p>At Faire, our teams and Engineering Managers are empowered to find the right processes that work for them. The rest of this blog will focus on my journey identifying some low cost, high value processes in the months after I started managing a team.</p><h3>Be nimble, stay curious</h3><p>I didn’t set out to redesign how my team worked. We just kept running into the same pain points:</p><ul><li>I couldn’t quickly tell where parallel project milestones stood.</li><li>We were doing heroic work, but not documenting it in a way that was legible to the rest of the org.</li><li>The team was drowning in maintenance work and bug triage.</li></ul><p>So I did what engineers do best: I experimented. I tried small process tweaks that felt lightweight, and I stayed alert to what was working and what wasn’t. I used my own frustrations as a signal. When I caught myself thinking, “Why can’t I see this at a glance?” or “This is taking way too long to explain,” I looked for ways to automate, template, or clarify.</p><p>Because these were experimental, I made sure the new processes added<strong> zero weight</strong> for the team. I took on the burden of bootstrapping everything — updating dashboards, maintaining documentation, refining templates — so others wouldn’t have to. Only once a process had clearly proven its value did I ask the team to help with upkeep, and even then, I stayed highly attuned to whether the maintenance cost still justified the impact.</p><p>And when it worked — when we had that <em>aha</em> moment as a team — it felt like liftoff.</p><h3>Low-cost, high-value process updates that worked</h3><p>I’m not going to claim these are universal best practices. Process is highly contextual. What worked for us might not work for your team. But here are a few examples of high-value, low-cost processes that I found to be effective.</p><h4>A project wiki for massive initiatives</h4><p><strong>The problem:</strong> We were tackling one enormous, half-year initiative sliced into 12 inter-locking milestones. Any slip in one milestone rippled through the rest — yet ownership, dependencies, and blockers were scattered across docs and DMs. Without a single shared view, the team couldn’t tell at a glance whether the entire project was still on track — or about to derail.</p><p><strong>The process:</strong> I created a lightweight wiki template that captured the essentials — milestones, blockers, dependencies, owners, and status. During daily stand-ups we reviewed only the milestone grid before touching individual tickets, using upcoming code-complete and launch dates as a quick “capacity gut-check.” When a crunch loomed, we either trimmed scope or shifted resources early.</p><p><strong>The results:</strong></p><ul><li>Sharper, more actionable status updates</li><li>Cleaner async communication (everyone referenced the same source of truth)</li><li>Early detection of schedule risk, keeping the team aligned and out of fire-drill mode</li></ul><p><strong>Cost-to-value ratio:</strong></p><ul><li>Cost: A few hours to design and socialize a simple wiki page</li><li>Value: Sustained visibility, faster decision-making, and fewer last-minute surprises</li></ul><figure><img alt="A Notion-style Gantt chart displaying engineering project timelines across September 2023. Projects like Guaranteed Shipping and various M1–M12 milestones are labeled with statuses such as “In progress” and “Done,” and assigned to specific team members." src="https://cdn-images-1.medium.com/max/1024/1*bUsL332wWa1Mdhrh6Zx6DA.png" /><figcaption>Screenshot of our project wiki — as evidenced by the milestone numbering, this was a living artifact.</figcaption></figure><h4>Tackling ticket backlog without burning out</h4><p><strong>The problem</strong>:<br>A mountain of bugs, support escalations, and tech-debt tickets was growing faster than we could take care of it.</p><p><strong>The process:<br></strong>We designated a weekly on-duty engineer — one person owns triage and drives P0/P1 issues to resolution, shielding everyone else’s focus. Any extra capacity is spent looking for long term foundational work to reduce the rate of incoming tickets.</p><p>We also launched bi-weekly bug-bash days — full-team swarm sessions to burn down older items and surface “easy wins.” This was a temporary measure to get our ticket backlog under control.</p><p><strong>The results:</strong></p><ul><li>P0/P1 tickets routed and resolved within SLA</li><li>Backlog shrank to a manageable queue</li><li>Engineers regained deep-work hours</li></ul><p><strong>Cost-to-value ratio:</strong></p><ul><li>Cost: One engineer per week on rotation, two half-days per sprint, &lt;1 day to spin up the dashboard.</li><li>Value: Restored focus, faster incident response, and a sustainable backlog</li></ul><figure><img alt="A dashboard titled “Shipping Issue Report” showing a priority breakdown of open shipping issues, filter counts for P0/P1 issues and SLA breaches, and line charts comparing issues created vs. resolved over the past 7 and 30 days." src="https://cdn-images-1.medium.com/max/1024/1*r7zn1U8g-xcSx7sQLJboIA.png" /><figcaption>Dashboard view of the Shipping Issue Report, highlighting issue priorities, SLA breaches, and resolution trends over time.</figcaption></figure><h3>What didn’t work</h3><p>Not all of our process ideas were smash hits. Here’s what we tried that didn’t make the cut — and what we did instead.</p><h4>Daily stand-ups → Hybrid async updates</h4><p><strong>What this was: </strong>Daily 15-minute standups meant for sharing blockers and having productive discussions.</p><p><strong>What went wrong</strong>: Our live standup turned into a roll-call of unproductive status updates.</p><p><strong>What we did instead:</strong> Kept synchronous stand-ups on Tuesdays and Thursdays and focused on conversations over updates. On the other days we post a quick Slack thread using a lightweight template:</p><figure><img alt="An automated slack message prompting the team to update JIRA statuses, fill out StatusHero, and post blockers/discussions in the thread" src="https://cdn-images-1.medium.com/max/948/1*e8jD10agZOYluWQz8tTOWQ.png" /><figcaption>The slack template we used to run async standups.</figcaption></figure><h4>Bi-weekly bug-bash days → Sunset</h4><p><strong>What this was: </strong>As mentioned above, this was a full-team swarm session to burn down on our out-of-control ticket backlog.</p><p><strong>What went wrong:</strong> This ritual was mission-critical while our backlog was towering. Once the queue shrank below our SLA threshold, corralling a dozen engineers for hours felt like busywork.</p><p><strong>What we did instead:</strong> Retired the session, celebrated the win, and replaced it with an automated alert that pings when open bugs breach a preset SLA.</p><h3>The right process is a moving target</h3><p>If there’s one idea I keep coming back to, it’s this: process should never be set-and-forget. What worked six months ago might be slowing you down today. Processes aren’t sacred — they’re tools, and like any tool they wear out, break, or stop being the right fit. What felt like rocket fuel last quarter might now be a dead weight.</p><h4>How to keep processes fresh and useful</h4><ul><li>Add a standing question to retrospective prompts: “Which process, template, or rule slowed us down this sprint?”</li><li>Slip a 2-minute “process friction” pulse into weekly one-on-ones: “Does anything feel heavier than its benefit right now?”</li><li>Implement expiration dates. Stamp new processes with a review date (e.g., 90 days) and calendar a quick “renew, refactor, or retire” discussion.</li></ul><h3>Thrusters only</h3><p>Great processes don’t feel like overhead. They feel like momentum.</p><p>They let your team move faster with less stress. They help you scale your judgment. They reduce the need to remember everything or re-decide the same thing over and over. And most importantly, they evolve with you. The best teams treat process exactly like code — meant to be iterated on, tested, and sometimes deleted outright.</p><p>Stop scrolling and set a five-minute timer — right now. Pick one pain point your team is facing today. Are there any low-cost, high-value processes that could help? Now pick one ritual or process your team treats as a given and run it through the value-vs-cost lens. Ask, “What would break if we killed it tomorrow?” If the honest answer is “not much,” congratulations — you just found your first anchor to cut.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b18deea53b0" width="1" height="1" alt=""><hr><p><a href="https://craft.faire.com/when-process-works-like-an-accelerant-not-a-tax-4b18deea53b0">When process works like an accelerant, not a tax</a> was originally published in <a href="https://craft.faire.com/">The Craft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>