The Human-First Engineering Toolkit
Everything you need to introduce, explain, and embed Human-First Engineering in a team or organisation.
The manifesto is what we believe. The framework is how we work. This toolkit is how you bring both of those into a real engineering culture without it becoming another box-ticking exercise.
🧰 What’s in the toolkit
- Implementation Guide — the rollout plan, ritual prompts, tooling baseline, reusable pitches, and quarterly review. Start here.
- Practices — concrete patterns for how engineers use AI tools day to day, aligned with Microsoft’s Hyper-Velocity Engineering.
- Slide Deck — a ready-to-present deck for a 30–45 minute team session. Markdown-based and compatible with Marp or any reveal.js-style renderer.
- Developer FAQ — the questions engineers actually ask. Honest answers, not corporate ones.
- For Early-Career Engineers — written for junior engineers, not about them. Practical habits for using AI to grow rather than stall.
- Relationship to HVE — how Human-First Engineering complements Microsoft’s Hyper-Velocity Engineering.
- Templates & Prompts — drop-in instruction files for GitHub Copilot and Claude, plus reusable prompts for framing problems, reviewing AI-assisted code, and assessing risk.
🗺️ How to use this toolkit
A reasonable order for most teams:
- Read the implementation guide end-to-end so you understand the shape of the rollout.
- Run the team session using the slide deck.
- Share the developer FAQ afterwards as a written reference.
- Embed the framework into your existing rituals as described in the implementation guide.
- Revisit quarterly.
đź”§ A note on adaptation
These materials are deliberately lightweight. Adapt them. Cut what does not fit your context. Add the examples that will land with your team. The goal is for the principles to be lived, not for the artifacts to be preserved.