Welcome to The Quiet Responsibility

Why this exists

A little over a year ago I wrote an article called The Quiet Responsibility. It was about everything a tech lead does that never appears in the job description: keeping standards coherent, closing decisions, building a sense of safety – the work that only shows when it isn’t done.

More pieces followed, and a pattern gradually became clear to me. What I had taken for standalone articles turned out to be one continuous theme with many entrances. The decisions that never get made. The standards that quietly erode. The AI that makes everyone an expert and no one aligned.

So now we’re doing it properly. Starting today, this is a steady body of work, with a rhythm, seasons, and a plan that stretches a year ahead.

What made that possible was mundane. My boss sent us a video about setting constraints rather than goals: Why The Smartest People I Know Set Constraints, Not Goals. It made me count what I already had: material sitting in my files, time I couldn’t bill to customers, and a company blog too small for me to keep filling on my own. That was enough to build something from.

What to expect

The rhythm: Two articles a week through a season. Tuesday (substance) and Thursday (sharper pieces, titles you’ll disagree with until you’ve read the text). From October, the first Friday of each month brings a long read from the futures series: where this profession is heading toward 2035. And between seasons we pause: this is meant to be something you have time to read, not a stream you drown in. September is the warm-up, so we’re publishing more often – Tuesday, Wednesday and Thursday – before settling into the regular rhythm.

The seasons: We open with The AI Age: how to lead a team where everyone has an expert in their pocket. From October 1, as Europe marks Cybersecurity Month, comes Security Autumn: twenty articles about the risk we keep calling debt. In spring comes something I’m especially looking forward to, but I’ll say no more about that now.

Two languages: Everything is published in Norwegian and English on the same day, because the profession is international and the conversation should be too. (Alt her publiseres på norsk også. Se etter språkvelgeren.)

Where to start

If you’re new here, these are the three entrances:

• The foundation: The Quiet Responsibility – the text everything else builds on
• If you’re leading through AI chaos: Tech lead in the AI age: From expert to frame-setter
• If the pace has gone quiet: Decision latency: When choices that aren’t made slow the team down

And tomorrow – Wednesday, as a small launch exception – comes an article for you, if you’ve just changed jobs: Your first 90 days as a new tech lead. September is, after all, the month of new beginnings.

The invitation

One more thing: this is not meant to be one-way.

The texts here will make claims. Disagree with them. Write to me, comment on LinkedIn, take the discussion into your own team and tell me where you landed. The best articles ahead will start in those conversations – the way the best standards start in a PR comment, not in a governance document.

And if you want it all in one place, you can sign up for The Tuesday Letter – one short email a week with the week’s texts and one gem from the archive.

See you tomorrow. And Thursday. That’s rather the point of a rhythm.