Standard : Engineers contribute meaningfully on day one
Purpose and Strategic Importance
This standard ensures engineers can make meaningful contributions from their first day, supported by streamlined onboarding, accessible documentation, intuitive tools, and a welcoming culture. It accelerates time-to-impact, boosts early confidence, and builds momentum in the developer journey.
Aligned to our "Developer Experience Matters" and "Foster Craftsmanship & Mastery" policies, this standard reduces friction, increases engagement, and ensures that new joiners quickly become productive members of the team. Without it, valuable time is lost, early motivation declines, and delivery suffers.
Strategic Impact
- Faster time to value for new engineers
- Higher satisfaction, engagement, and retention rates
- Reduced onboarding friction and duplicated effort
- Improved team cohesion and confidence in delivery
- Greater consistency in standards, tools, and practices
Risks of Not Having This Standard
- Increased onboarding time and reduced early productivity
- Fragmented or outdated documentation and tooling
- Declining team morale and poor first impressions
- Higher risk of early attrition or delayed ramp-up
- Wasted time spent rediscovering how things work
CMMI Maturity Model
Level 1 – Initial
| Category |
Description |
| People & Culture |
Onboarding is informal and reliant on individual goodwill or tribal knowledge. |
| Process & Governance |
No standard process exists for onboarding or early contributions. |
| Technology & Tools |
Tools are not pre-configured or require manual setup. |
| Measurement & Metrics |
No tracking of onboarding experience or time-to-impact. |
Level 2 – Managed
| Category |
Description |
| People & Culture |
Teams recognise onboarding challenges and start documenting helpful steps. |
| Process & Governance |
Basic onboarding materials and walkthroughs are provided. |
| Technology & Tools |
Some tooling and environment setup is pre-defined but not fully automated. |
| Measurement & Metrics |
Time to first commit or deployment is occasionally reviewed. |
Level 3 – Defined
| Category |
Description |
| People & Culture |
New joiners feel supported and encouraged from day one. |
| Process & Governance |
Standard onboarding processes are defined, shared, and regularly reviewed. |
| Technology & Tools |
Environment setup is automated with pre-configured tools and access rights. |
| Measurement & Metrics |
Onboarding metrics (e.g. time to first contribution) are routinely tracked. |
Level 4 – Quantitatively Managed
| Category |
Description |
| People & Culture |
Teams proactively improve onboarding through structured feedback loops. |
| Process & Governance |
Onboarding programmes are iterated based on data and performance outcomes. |
| Technology & Tools |
Tooling supports sandbox environments, guided walkthroughs, and automation. |
| Measurement & Metrics |
Time-to-impact and onboarding satisfaction are measured across teams. |
Level 5 – Optimising
| Category |
Description |
| People & Culture |
Onboarding is part of a culture of mastery, mentoring, and rapid enablement. |
| Process & Governance |
Continuous improvement processes optimise for consistency and delight. |
| Technology & Tools |
AI assistants, self-service platforms, and feedback-driven improvements guide onboarding. |
| Measurement & Metrics |
Engineering impact on day one is normalised and used as a benchmark. |
Key Measures
- Median time to first meaningful contribution (e.g. merged PR, deployed change)
- Onboarding satisfaction and feedback scores
- Onboarding completion rates across teams
- Tooling and access setup time
- Attrition rates within first 90 days