<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Jere Syrjälä: decision log</title><description>Consequential product and org decisions with context, the call, the outcome and what was learned. New and updated cards, including status changes.</description><link>https://jeresyrjala.com/</link><language>en</language><docs>https://www.rssboard.org/rss-specification</docs><item><title>D-016 [open] Make the release call from test evidence instead of hiring QA</title><link>https://jeresyrjala.com/decisions/d-016/</link><guid isPermaLink="false">D-016@2026-11-05</guid><description>Infrakit, 2026-11, Release quality. Context: With AI-assisted building, more changes reach a release faster. Leadership wanted someone to own the overview of release quality. The obvious answer was a dedicated QA hire. Decision: Proposed that I make the go/no-go call for releases, based on test data (which tests exist and what they show) plus my view of customer cases and how fragile they are, with end-to-end and regression tests part of the developers&apos; definition of done. Hypothesis: Releases that hurt fragile customers become rare. Missing test evidence is visible before a release, not after it. The call does not turn into a queue waiting on me. Confidence: 60%. Review date: 2027-06-01.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>open</category><category>infrakit</category><category>Release quality</category></item><item><title>D-015 [open] Organise the product team around customer jobs, not around who builds</title><link>https://jeresyrjala.com/decisions/d-015/</link><guid isPermaLink="false">D-015@2026-11-05</guid><description>Infrakit, 2026-11, Team design. Context: AI made building fast. Scoping and understanding customers did not get faster with it. Developers waited on coordination for small UX calls, and roadmap trade-offs tended to go to whoever pushed hardest. Decision: Proposed a team model where developers own small UX through weekly dogfooding and monthly customer contact, dedicated project coordination is kept only for rehauls and new products, and every customer job sits in a state matrix with a fixed number of coordination slots. Hypothesis: Leadership makes its trade-offs openly against the matrix. Small UX ships without waiting for anyone. Rehauls and new products actually finish because coordination is not spread thin. Recurring bug clusters stop coming back once they are treated as rehauls. Confidence: 75%. Review date: 2027-06-01.</description><pubDate>Thu, 05 Nov 2026 00:00:00 GMT</pubDate><category>open</category><category>infrakit</category><category>Team design</category></item><item><title>D-011 [did_not_work] Ship MVPs one after another and trust a few users to pull the product</title><link>https://jeresyrjala.com/decisions/d-011/</link><guid isPermaLink="false">D-011@2026-11-18</guid><description>Taskshare, 2021-06, Product discovery. Context: Early-stage product, small team, strong building capacity. Decision: Built MVPs one by one, assuming a good product plus a couple of users would be enough to find the way forward. Outcome: Too much time went into building and too little into understanding the problem. New versions shipped before the previous one had been pushed to its limits. Learned: Take the first version so far with users that it almost hurts, until they want something so badly the MVP can&apos;t do it. Only then build the next one.</description><pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate><category>did_not_work</category><category>taskshare</category><category>Product discovery</category></item><item><title>D-012 [did_not_work] Deploy the team widely and let people run on their own</title><link>https://jeresyrjala.com/decisions/d-012/</link><guid isPermaLink="false">D-012@2026-11-18</guid><description>Taskshare, 2020-09, Team leadership. Context: Founder at 22, leading a team of about 10. Decision: Spread people across areas and did not follow up closely on how their work was going. Outcome: People were left alone with their work, and the standard was not set by me. Learned: A leader sets the standard by getting close to everyone&apos;s day-to-day work, out of care and to help them do better, not to micromanage.</description><pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate><category>did_not_work</category><category>taskshare</category><category>Team leadership</category></item></channel></rss>