Managing Teams: Staffing, Inceptions and Psychological Safety
In a conversation with Brett Harned, agile delivery manager Neil Vass of Co-op Digital in Manchester explains how teams are formed, aligned and supported over time. The episode runs about 31 minutes and is episode 15 of season 2.
Start small, then build a lasting team
Talented groups do not always gel on their own. Vass describes a deliberate approach: begin with a discovery team, learn what is needed, and then grow a durable product team. That sequence avoids locking in a large staffing plan before the work is understood.
A practical checklist for the first weeks:
- Start small and test the problem before scaling the team.
- Plan for continuity once a product team is formed, since rebuilding it carries a high cost.
- Use communities of practice to compare capability needs across teams and identify gaps earlier.
- Keep objectives few, visible and refreshed, with stakeholders agreeing on what success looks like.
- Choose a single team problem to improve at a time, so progress stays visible.
Use inceptions to agree how to work together
An inception should last more than a kickoff meeting. Vass recommends spending multiple days agreeing working practices as well as delivery plans. Exercises such as writing a personal user manual help colleagues understand preferences, strengths and pressure points. An empathy survey used in a retrospective serves a similar purpose: it makes different perspectives explicit.
The underlying idea is simple: when people consider how others experience the work, collaboration improves. Revisit the agreements regularly, because a working agreement that suited the first month may not suit later stages.
Motivate through safety, not authority
Motivation does not depend on formal line authority. Vass links it to psychological safety — the confidence to flag what is not working. That candour matters more than assembling a perfect skills mix, because problems surface while they can still be addressed.
For managers without direct authority, useful moves include naming one improvement priority, inviting feedback on working agreements, and using cross-team communities to share learning. The episode also covers identifying team strengths and weaknesses, aligning around organisational and project goals, and low-effort habits that keep morale and output steady.
What the episode covers
The conversation covers staffing practices, spotting strengths and weaknesses, alignment around goals, motivation without line management, team-building exercises, and small routines that sustain a positive, productive atmosphere. A quote attributed to Dr. W. Edwards Deming was also mentioned during the discussion.
| Practice | Purpose | Check |
|---|---|---|
| Discovery team first | Learn before committing a full team | Is the problem understood before scaling? |
| Multi-day inception | Agree working practices, not only deliverables | Have personal manuals and agreements been revisited? |
| Communities of practice | Surface skills gaps across teams | Are gaps shared and acted on across teams? |
| Few, live OKRs | Keep goals aligned and current | Do stakeholders define success the same way? |
| Psychological safety | Let people raise problems early | Is one team problem being improved at a time? |
Practices described by Neil Vass for Co-op Digital in the episode; adapt to your own context.
Frequently asked questions
How should a new team be staffed?
Start with a small discovery group, then expand into a stable product team instead of committing people a year ahead. Because changing a formed team is costly, the early shape matters.
What should a team inception cover?
Use a multi-day inception to agree how the group will work together, not only what it will deliver, and revisit those agreements during retrospectives.
How can managers spot skills gaps across teams?
Communities of practice, where people across teams compare needs and share learning, were described as the strongest way to surface capability gaps.
How should OKRs be kept useful?
Keep the objective set small and current, and check that stakeholders share the same definition of success.
What matters more than the skills mix?
Focus on psychological safety first: people need to raise problems early. Then improve one team issue at a time rather than trying to fix everything at once.