The 30-Minute Growth 1:1

A growth 1:1 is a recurring private conversation that improves trust, judgment, context, and development. It is not the team's status meeting, the performance-review ceremony, or the only place feedback can happen.

Manager Tools treats recurring one-on-ones as a foundational management practice and puts the direct report's topics first. GitLab emphasizes a shared agenda and separates career development from routine updates. This course combines those practitioner ideas into one fixed structure for senior engineers.

The course's synthesized standard is exactly 30 minutes, split into three fixed ten-minute segments. That constraint protects the engineer's voice, ensures useful manager input, and reserves time for future growth instead of hoping it survives whatever is urgent.

Asynchronous status means progress, metrics, risks, and routine dependencies are written where people can read them without a meeting. The 1:1 may discuss the human or decision problem behind a status item, but it does not replay information already available.

Compare these prompts:

The engineer owns the opening segment because information closest to the work is easy for a manager to miss. Good topics expose judgment, friction, relationships, confidence, energy, or a decision—not merely tasks.

Engineer preparation prompts:

• What is taking more energy than it should?
• Which decision feels stuck, and what have I already tried?
• Where am I receiving conflicting signals?
• Whose context or trust do I need?
• What do I want the manager to understand, decide, or do?

Manager behavior: listen long enough to learn, ask what outcome the engineer wants from the topic, and resist solving before the problem is clear.

Useful opening script: “I have two topics: a disagreement about the data contract and my pattern of taking back delegated work. I want perspective on the first and coaching on the second.”

The manager owns the middle segment to provide information and observations the engineer cannot get alone. Feedback here means a specific observed behavior, its effect, and a possible next action—not a label about personality.

Use this compact feedback script:

“When [observable behavior] happened in [context], the effect was [specific impact]. What was happening from your perspective? Next time, would you try [behavior] so we can observe [desired effect]?”

Example: “In Tuesday's design review, you answered each objection before the service owners finished explaining it. Two owners stopped contributing. What was happening from your perspective? Next time, would you summarize the concern before offering your view so we can test whether participation improves?”

Context can include changing business priorities, stakeholder incentives, decisions made elsewhere, or why a promising project is no longer important. Share enough context for judgment without exposing confidential information.

The final segment converts discussion into development. Future growth means one capability tied to a real organizational outcome, with an opportunity, support, evidence, and next action.

The engineer might say: “My growth hypothesis is cross-team alignment. I propose framing the logging-retention decision with Security and Finance. I need introductions and confirmation that I can convene the decision.”

The manager might answer: “I will make both introductions by Thursday and tell the directors you own the recommendation. Bring the decision criteria and dissent, not a predetermined solution. We will inspect stakeholder feedback in the next 1:1.”

Close by reading the actions aloud. “Engineer: draft criteria by Tuesday. Manager: introductions by Thursday” is stronger than “circle back on logging.”

A shared page preserves continuity without turning the meeting into bureaucracy. Keep it short enough to update before and during each conversation; sensitive personal notes should follow company policy and remain outside broadly visible project systems.

# Growth 1:1 — Engineer / Manager

## Next meeting
### 0–10 Engineer agenda
- Topic — desired outcome: perspective / decision / coaching / context

### 10–20 Manager context and feedback
- Context:
- Observation → effect → question → next behavior:

### 20–30 Future growth and actions
- Capability and opportunity:
- Evidence to inspect:
- Engineer action — date:
- Manager action — date:

## Async status
- Link to project update; do not repeat it here

## Running evidence and open loops
- Outcome / contribution / corroboration

The template intentionally repeats the fixed segments. Either person can add topics in advance, and both can see unresolved actions before the next meeting.

A stable format makes drift visible. When the conversation becomes status-only, manager-only, or action-free, name the drift and reset the next meeting rather than redesigning the whole system.

The 1:1 becomes a reliable growth interface when its purpose and boundaries stay stable. The fixed structure is this course's synthesis of the cited practices.

• The standard meeting is exactly 30 minutes with fixed 10/10/10 segments.
• Engineer agenda comes first; manager context and feedback come second; future growth and named actions come third.
• Routine project status stays asynchronous.
• Feedback should be specific and timely, not saved for a surprise review.
• Longer sensitive topics receive a separate conversation rather than consuming a segment.
• Both manager and engineer leave with visible actions, owners, and dates.

This checklist makes the meeting usable immediately. Both people complete their side before the calendar event begins.

Engineer:

• [ ] Add one or two topics and the outcome wanted from each.
• [ ] Link the asynchronous status update rather than copying it.
• [ ] Bring one growth opportunity, evidence point, or support request.

Manager:

• [ ] Read the shared page and status update.
• [ ] Prepare one piece of context and one evidence-based observation.
• [ ] Check the last manager action and complete or explain it.

Both:

• [ ] Protect exactly 30 minutes.
• [ ] Follow 10/10/10.
• [ ] End with actions, owners, and dates.

These practitioner sources inform the meeting principles; the exact 30-minute Growth OS 10/10/10 is a clearly labelled course synthesis.

• Manager Tools: One-On-Ones, updated Part 1
• Lara Hogan: Questions for our first 1:1
• Lara Hogan: One-on-one resources
• GitLab Handbook: 1-1