People carry the change — or it does not happen.
People, recruiting & culture
Technical change is always a people question too. We fill roles, build teams and work on the leadership practice that carries both.
What we offer
- Recruiting and placement for technical and hybrid roles
- Clarifying mandate, decision rights and success criteria before the search starts
- Team building in distributed and asynchronous setups
- Work on leadership, psychological safety and sustainable ways of working
Why it matters
Transformation projects need roles the organisation has no template for. Deriving them from existing job descriptions fills a position next to the actual task.
Psychological safety is not a comfort topic here. It is the precondition for problems being reported early — and therefore a direct factor in project success.
Articles on this topic
All articles →People & cultureFoundation
Teams that carry transformation: psychological safety is not a comfort topic
In digital initiatives it is not a team's motivation that decides the outcome, but whether bad news travels upwards early. On psychological safety, leadership and recruiting in transformation contexts.
People & cultureField notes
Ownership instead of roles: who is really accountable after go-live
A system goes live. Three months later nobody knows who is accountable for a critical failure. The difference between a role and ownership is the difference between a system that runs and one that lands.
People & cultureNote
Twelve roles become three: what Gartner's team shapes mean for provability
Gartner expects smaller engineering teams. The role map behind it mostly removes translation roles — and with them the places where decisions used to get written down as a side effect.