Apex BrandU
• October 11, 2026
Published /u/tewhalen1/blog/turn-1-1s-into-professional-development-framework

10 Practical Moves to Turn 1:1s Into Professional Development

Highlight
Use your existing 1:1s for professional development by picking one skill target, defining proof of progress, and ending every meeting with a small next practice—not another status dump.

Use your existing 1:1s for professional development by picking one skill target, defining proof of progress, and ending every meeting with a small next practice—not another status dump.

Why status-only 1:1s stall your growth

If you already have regular 1:1s but leave with project updates instead of skill gains, you are not alone. Mid-career individual contributors often treat the meeting as a report-out. Professional development needs a different structure: one clear skill, visible practice, and a short feedback loop.

Use this ten-part framework inside the meetings you already have. No new courses required—just better questions and tighter follow-through.

The 10-part 1:1 professional development framework

1. Name one growth skill for the next 90 days

Pick a single capability tied to your role, such as stakeholder framing, technical design reviews, or written decision memos. One focus beats a vague “get better” list.

2. Define what “good” looks like in plain language

Write two or three observable behaviors. Example: “I can present tradeoffs in under five minutes without reading slides.” Shared clarity prevents fuzzy feedback later.

3. Convert status time into skill time

Keep project updates to a short written note before the meeting. Protect live minutes for practice, coaching, and decisions about your growth skill.

4. Bring one real work sample each time

Use a draft email, design note, or meeting agenda from the past week. Concrete artifacts make coaching specific instead of abstract advice.

5. Ask for one targeted observation

Request feedback on a single dimension: clarity, prioritization, risk callouts, or audience fit. Narrow asks produce usable notes you can act on next week.

6. End with a micro-practice, not a vague goal

Agree on one small rep before the next 1:1—run a dry-run, rewrite a summary, or lead one agenda item. Tiny practice compounds faster than big intentions.

7. Track proof, not vibes

Keep a simple log: date, practice, what improved, what still felt hard. Review it monthly so progress is visible when promotions or role talks arrive.

8. Link the skill to upcoming work

Map your target skill onto a live project milestone. Stretch inside real deliverables so development stays practical and manager-supported.

9. Revisit blockers without turning into venting

Name one obstacle—unclear ownership, missing review time, or overloaded calendar—and ask for one adjustment. Keep the focus on enabling practice.

10. Reset the skill when evidence says you are ready

When your proof log shows consistent results, graduate the skill and choose the next one. Professional development stays fresh when the framework recycles on purpose.

How to start this week

Before your next 1:1, send a three-line note: the skill you are building, the work sample you will bring, and the micro-practice you want feedback on. That single habit shifts the meeting from status theater to deliberate growth.

You do not need a perfect plan. You need a repeatable loop: focus, practice, feedback, proof. Run it inside the 1:1s you already have, and professional development becomes part of the job instead of a side project you never start.

Next Step

Want help turning this into action? Save this page, compare it to your current brand, and decide what needs to become clearer next.

Follow along with tewhalen1 for more practical guidance.

One curiosity-driven next step
No pressure. Just a fast clarity check.

Take 60 seconds and scan this post again for one thing: what they clearly prioritize, and what they ignore.

  • Headline test: what promise do they lead with?
  • Mechanism test: what do they say “works” (without hype)?
  • Proof of focus: do they repeat one message everywhere?

Then come back and compare what you noticed to the framework in the post.