Developing an established team — without running it over
Development starts where existing routines are questioned, not at the program decision.
INSIGHTS
Here I write about patterns I have encountered in over 25 years of project work: what works, what fails, and what I take away from it.
Established companies face a different question than startups: not "how do we build a team?", but "how do…
12. October 2026
Why do some organizations do what they do, and others merely become it? Simon Sinek's Golden Circle answers…
12. October 2026
Leadership in technical organizations is a balancing act. Deliver company goals without wearing the team down. Deliver operational…
12. October 2026
Early in a young company, something decides more about later success than any technology choice: how the team…
12. October 2026
The move from expert to leader is one of the turning points in a career, and one of…
12. October 2026
Development starts where existing routines are questioned, not at the program decision.
WHY, HOW, WHAT — a useful thinking pattern, usually applied wrong. Three tests that decide.
A process is not finished when it is documented. What it takes to move a process from paper into daily work — and why most stall right there.
Why changes lose momentum after the kick-off, and what anchoring actually takes.
Agile frameworks don’t solve problems, they expose them. When agile helps, and when it doesn’t.
The tension never disappears, but it can be led. Three fields every leader knows.
Decision and communication are done quickly. The everyday work after that is the real effort.
How the team works together decides more about success than any technology choice.
The technology is rarely the bottleneck. Three patterns that stall projects, and what helps early.
What really changes when you take on a leadership role, and where good experts stumble.