01 / FROM
Being the answer
Useful when you are an individual contributor. Risky when every decision waits for you.
For first-time technical leaders
Stop fixing. Start leading.
You were promoted because you solve problems. Now your job is building a team that can solve them without you.
Free founding membership. Realistic scenarios, conversation scripts and a first-30-days plan for engineers, IT specialists and technical team leads.
leadership.diff
Situation: A pull request has been stuck for two days. You know how to fix it in ten minutes.
−Fine, I’ll just fix it tonight.
+What’s blocking it, and what help do you need to finish it tomorrow?
One solves this bug. The other builds a team that can solve the next one.
Your job changed. Nobody sent the manual.
Technical skill got you here. Now the work is clarity, trust, prioritisation and judgement — usually while still being expected to deliver.
02 / TO
Building capacity
Give people context, ownership and support.
03 / THE RESULT
A team that can move without you
Less rescuing. Better decisions. More room to think about what comes next.
Practise the moments that actually happen.
Members choose their response, see how each approach plays out, and keep private notes. New scenarios are released every week.
Scenario 01 · Delegation
Your strongest engineer keeps rescuing everyone
✕ Tempting move
Thank Sam publicly for keeping the release on track and ask them to review all high-risk changes going forward.
✓ Stronger move
Meet Sam privately, acknowledge the value they add, and agree two areas where Sam will coach someone else through the problem instead of fixing it.
Why it works: This respects Sam's contribution, addresses the burnout signal and converts rescuing into teaching. It builds capacity without removing the safety net overnight.
Scenario 02 · Accountability
The same deadline has slipped for the third time
✕ Tempting move
Quietly take the remaining work yourself so the dependent team is not let down again.
✓ Stronger move
Name the pattern in a private conversation, ask what is actually getting in the way, and agree a smaller checkpoint before Friday.
Why it works: Naming the pattern without judging the person keeps the conversation useful. A near checkpoint gives you early warning rather than another Friday surprise.
Scenario 03 · Authority
A former peer ignores a decision you made
✕ Tempting move
Let it go for now. The relationship matters more than the process, and Alex will probably come around.
✓ Stronger move
Talk to Alex directly: acknowledge the change in your relationship, invite genuine objections, and make clear that once decided, you need follow-through.
Why it works: This separates disagreement, which is welcome, from non-compliance, which is not. Acknowledging the awkwardness out loud usually reduces it.
Scenario 04 · Coaching
Every one-to-one becomes a status update
✕ Tempting move
Cancel the one-to-ones. The team already reports status in stand-up, so they are duplicating effort.
✓ Stronger move
Keep status out of the meeting and open with a question about what is making their job harder than it needs to be.
Why it works: Moving status elsewhere signals the meeting is theirs. An open question about friction surfaces issues that never appear on a board.
Founding membership · free
The First Lead Kit
What to say, decide and do in your first months leading a technical team.
Built for Monday morning, not a leadership retreat.
01
Interactive scenarios
Choose a response, see the trade-offs of each option and learn the principle behind the stronger move.
02
New scenarios every week
A growing library covering delegation, feedback, accountability, conflict, priorities and managing up.
03
Conversation scripts
Plain-language wording you can adapt for difficult conversations.
04
Your first 30 days
A practical checklist that tracks your progress as you settle into the role.
05
Private reflection notes
Capture how each situation applies to your team. Only you can see them, and you can export or delete them any time.
This is for you if…
- You recently became a team lead, engineering manager or IT manager.
- You still have delivery work but now carry responsibility for other people.
- You want practical words and decisions, not generic motivation.
It is not…
- An accredited qualification or HR advice for your organisation.
- A replacement for your employer’s policies or legal guidance.
- A promise of promotion, pay rises or instant confidence.
Join as a founding member.
Membership is free while we build the library. Create an account to start the scenarios, track your first 30 days and help decide what we cover next.
No payment details required. You can delete your account and data at any time.
Create your free account →Already a member? Log in
Questions
Is it really free?
Yes. Founding membership is free and we do not ask for payment details. If we introduce paid features later, we will tell members in advance and nobody will be charged without choosing to buy.
Who writes the material?
The scenarios are written from practical experience leading technical teams. Situations are composites; names and details are invented.
Is this only for software engineers?
No. It is designed for people leading technical work — including infrastructure, cyber security, data, support and IT operations teams.
What happens to my notes?
Your notes are private to your account. You can download everything we hold about you, or delete your account permanently, from your account page.