Your best manager’s standard, on every team.
In a fully powered people team, each hiring manager starts recruiting from a role brief agreed with the people lead. Each new colleague arrives to a plan that says what productive means at day 30, 60 and 90. Each manager walks into a feedback conversation with dated examples, good questions and last time’s promises in front of them. Each colleague watches their development plan move.
Today that standard usually lives with one or two managers, and the people lead knows exactly who they are. Put their preparation in front of every manager, in the AI the company already pays for, and you 10X what your people team can do.
Start from the outcome, then map the work.
Take an invented 120-person freight and warehousing company: two warehouses, a transport desk, a customer operations team of fourteen and a small office. The people function is a people lead and a people coordinator. Managers across five teams recruit, onboard and develop their own people, each in their own way.
Start from the outcome the company wants: the right person in each role, productive sooner and growing in it. Then map the work that crosses teams. Recruiting passes between the hiring manager and the people lead. Onboarding reaches IT, the warehouse floor and a buddy on the team. Feedback runs between a manager and a colleague, and development runs back into the next conversation. An AI org chart that shows the work between teams lands each piece on the role that does it, instead of filing everything under HR.
The capability map.
Five capabilities cover recruit, train and develop. Each row names who starts it, what it prepares, who decides and what it hands on.
Illustrative example with invented data. The invented freight and warehousing company.
| Capability | Who starts it, with what | What is prepared | Who decides | Hands to next |
|---|---|---|---|---|
| Role brief | Hiring manager, with the team’s outcomes and what the role must deliver by day 90 | Responsibilities, day-90 expectations, the evidence interviews must gather | Hiring manager and people lead agree the brief; people lead sets the pay range | Interview plan; responsibilities to onboarding |
| Interview plan | People lead, with the agreed role brief | Questions and a work sample for each responsibility; an interviewer notes template | Interviewers assess; hiring manager decides the hire; people lead approves the offer | After the hire, the start date to onboarding |
| Onboarding plan | Hiring manager, with responsibilities, training material and start date | First week, milestones at day 30, 60 and 90, people to meet, check-ins | Manager adapts it and judges progress; new colleague shapes it | Milestones to feedback preparation |
| Manager feedback preparation | Team manager, with dated observations and last time’s commitments | Observations, questions, the ask, support; weak observations sent back | Manager holds the conversation; manager and team member agree the plan | Development plan to follow-through |
| Development follow-through | Team member, monthly, with the agreed plan and their progress notes | Progress on each commitment, support received, items for next time | Team member and manager agree progress; people lead runs pay and promotion | Commitments to the next feedback preparation |
Each row feeds the next. The role brief’s responsibilities become the onboarding plan’s starting point and the yardstick for every feedback conversation. The follow-through becomes the next conversation’s commitments. The people lead maintains the standard behind each row, and the work lands on the managers and colleagues who do it.
Two rows are written up as capability templates you can read now: the employee onboarding plan and manager feedback preparation.
Where the people decide.
Every row marks who decides, and the line sits in the same place each time. The capabilities prepare the work around people decisions. They never screen, rank, score or reject an applicant. Choosing who to hire, setting pay, rating performance, promoting and ending employment stay with the hiring manager, the team manager and the people lead. So does any employment document with legal effect, such as an offer letter or a severance agreement.
Managers keep every decision and get better preparation for each one. The People and HR and Recruiting and hiring pages show more of the work around those decisions, from workforce plans to interview arrangements.
One prepared output, with an exception.
Here is one feedback preparation in full. The customer operations manager supplied a coordinator’s agreed responsibilities, four observations and the commitments from their last conversation. The preparation used two observations and sent two back.
Illustrative example with invented data. Shipment numbers, dates and notes are invented.
Feedback preparation · Customer operations coordinator · Wednesday 4 November 2026
- Prepared for
- The customer operations manager. Conversation booked for 45 minutes.
- Responsibility in focus
- Responsibility 3: keep customers informed of confirmed delivery changes.
- Start with
- 21 October: the night-desk handover note covered six open exceptions, each with its next action and owner. The night desk closed four without calling anyone. Source: handover note and night-desk log.
- Observation
- 14 October: on Shipment 5531, the coordinator gave the customer a new delivery window before the carrier confirmed it. The confirmed window was three hours later. Source: case notes and the carrier’s confirmation.
- Interpretation to test
- The manager’s note: “Wanted to reassure the customer.” Ask; do not state.
- Questions
- Walk me through Shipment 5531: what did you know when you called? What would have made waiting easier? The 21 October handover worked. What did you do that the team could reuse?
- The ask
- Before giving a customer a new delivery window, confirm it with the carrier, or tell the customer it is unconfirmed and when you will call back.
- Support on offer
- Pair with the buddy on the next two delay cases. Access to the carrier portal’s delivery reports.
- Last time, 9 September
- Coordinator to shadow the transport desk for two afternoons: done on 17 and 24 September. Manager to arrange carrier-portal report access: still open. Resolve it before Wednesday, or say when it will be done.
- Sent back
- “Needs to be more proactive with the warehouse.” No date and no example: what happened, when, and with what effect? “The warehouse team said the coordinator was short with them.” Second-hand: did you see it? If not, ask the warehouse shift manager to raise it directly, or leave it out.
Preparation for the manager. The manager holds the conversation; manager and coordinator agree the development plan together.
The two returned observations matter most. A vague note turns feedback into an argument about impressions. A second-hand one asks the colleague to answer someone who is not in the room. The preparation sends both back with a question the manager can answer in a minute. It also puts the manager’s own open commitment on the page, where follow-through starts.
Prove it on one role, then roll it out.
Start with one role and one team. Agree the role brief, run the onboarding plan on the next start, and prepare the first few feedback conversations with the managers who will hold them. Build the plan with the people who do the work: the managers and colleagues involved decide what a usable observation is and what productive means at day 30. Then roll it out team by team.
We help your organization strategically plan and migrate to AI without losing control of how the work gets done. Fully Powered works across ChatGPT, Claude, Copilot and Gemini. Each capability runs in the AI your company already uses, at your pace, and the people lead owns the standard behind it.
Bring the role you hire for most often and the way your managers prepare for one-to-ones today.