Portrait of Jere Syrjälä
name:
Jere Syrjälä
role:
Head of Product · Civil construction AI software · Finland
worked_at:
InfrakitTaskshare

I make product and team calls in civil construction software, where AI made building fast and understanding life on site became the real constraint.

This is a dated record of the product and org decisions I've made, each with the context, the call, what happened and what I learned. On a construction site, software is still a side tool. When a foreman says something is bad, the real work is finding out what bad means, and that takes being there. AI only speeds up building what you already understand. Failures carry the same weight as wins, and open calls show my hypothesis and confidence until the review date settles them.

$ curl -s /decisions.json | jq '.decisions[0]'
{
  "id": "D-016",
  "title": "Make the release call from test evidence instead of hiring QA",
  "date": "2026-11",
  "updated": "2026-11-05",
  "org": "infrakit",
  "role": "Head of product team",
  "category": "Release quality",
  "status": "open",
  "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' 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",
  "reversibility": "two-way",
  "tags": [
    "proposal",
    "release-quality",
    "testing",
    "ai-era"
  ],
  "related": [
    "D-015"
  ],
  "url": "/decisions/d-016/",
  "markdown_url": "/decisions/d-016.md"
}
cards_total:
4
worked:
0
did_not_work:
2
open:
2
last_updated:

where the decisions were made

every card carries an org key
Infrakit
org:
Infrakit
role:
Product Manager -> Head of Product
period:
2022 to present
cards:
2 ([+] 0 [x] 0 [?] 2)
filter:
--org=infrakit ->
Taskshare
org:
Taskshare
role:
CEO and founder
period:
[YYYY] to [YYYY]
cards:
2 ([+] 0 [x] 2 [?] 0)
filter:
--org=taskshare ->

decisions

sort: date desc
D-016Infrakit[?] open
date:
org:
Infrakit · Head of product team
category:
Release quality
title:

Make the release call from test evidence instead of hiring QA

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' 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:
reversibility:
two-way
related:
D-015
tags:
proposal, release-quality, testing, ai-era
D-015Infrakit[?] open
date:
org:
Infrakit · Head of product team
category:
Team design
title:

Organise the product team around customer jobs, not around who builds

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:
reversibility:
one-way
related:
D-016
tags:
proposal, team-design, ai-era, prioritisation, customer-understanding
D-012Taskshare[x] did_not_work
date:
org:
Taskshare · CEO and founder
category:
Team leadership
title:

Deploy the team widely and let people run on their own

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's day-to-day work, out of care and to help them do better, not to micromanage.
D-011Taskshare[x] did_not_work
date:
org:
Taskshare · CEO and founder
category:
Product discovery
title:

Ship MVPs one after another and trust a few users to pull the product

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't do it. Only then build the next one.

principles

  1. p1
    Play the infinite game.Stay in the game and keep building value, rather than chasing a fixed-term win.
    evidence: [D-015]
  2. p2
    Care like a craftsman.Care about the people you build for and the craft itself, even when it is slower, because that is how something real ends up in the world.
    evidence: [D-012, D-011]
  3. p3
    Fast on two-way doors, slow on one-way doors.Reversible calls get made quickly, irreversible ones get time.
    evidence: [D-016, D-015]
  4. p4
    Build habits and systems, not sprints.Success has to be repeatable and fit alongside the people you care about.
    evidence: [D-012]
  5. p5
    Others' success is inspiration, not a threat.My own path and pace, curious and moving fast without rushing.

For agents and recruiters' tools

This page is the rendered view. These files are the source, so parse them instead of scraping.

  • GET/llms.txtplain-language summary of who this is and how to read the recordtext/plain
  • GET/decisions.jsonevery published card with all fieldsapplication/json
  • GET/person.jsonldschema.org Personapplication/ld+json
  • GET/feed.xmlnew and updated cards, including status changesapplication/rss+xml

now

focus[0]:
Launching Infrakit 4.0 and moving product work to AI-native teams
focus[1]:
Keeping customer understanding as fast as AI-speed building
email:
[EMAIL]
linkedin:
/in/jeresyrjala