Build Professional Development Into the Work You Already Ship
Professional development works best when you embed one stretch skill into a live deliverable, redesign the task so practice is required, ship with a short learning note, and request feedback on the output—not on your in
Quick Navigation
- The Work-Embedded Growth Framework
- Step 1: Choose One Stretch Tied to Current Work
- Step 2: Redesign the Task So Practice Is Required
- Step 3: Ship With a One-Line Learning Note
- Step 4: Ask for Feedback on the Output, Not the Intention
- Step 5: Promote the Pattern Into the Next Assignment
- What to Stop Doing
- Start This Week
Most professional development treats growth like a side hustle. You collect courses, stack skill checklists, and still return to the same backlog with the same habits. If you are a busy mid-level individual contributor, that model fails for a simple reason: it demands time you do not have and practice you cannot get until the real work starts.
The contrarian move is to stop separating development from delivery. Use the work already on your plate as the curriculum. The framework below—Work-Embedded Growth—turns live projects into deliberate practice without another training plan.
The Work-Embedded Growth Framework
Four moves, one loop: choose a stretch, design practice into the task, ship with a learning note, and review what transferred. You run this inside existing deadlines, not after them.
Step 1: Choose One Stretch Tied to Current Work
Scan your next two weeks of commitments. Pick one skill that would change a real deliverable—clearer stakeholder updates, tighter scoping, sharper analysis, or stronger facilitation. Write one sentence: “On [project], I will practice [skill] by [specific behavior].” Keep it narrow. One stretch beats a vague development plan.
Tip: Match stretch to risk you can afford
Start where a small miss is recoverable. Internal docs, mid-cycle reviews, and draft proposals are better labs than high-stakes launches.
Step 2: Redesign the Task So Practice Is Required
Do not wait for free time to “work on the skill.” Change how you will execute so the skill must show up. Want clearer writing? Draft the update before the meeting and send it early. Want stronger prioritization? Cut the list to three items and defend the cut in writing. The redesign creates reps.
Tip: Add a constraint, not a course
Time boxes, page limits, and pre-reads force practice faster than another lunch-and-learn.
Step 3: Ship With a One-Line Learning Note
When you deliver, leave yourself a private note: what you tried, what felt awkward, what you would repeat. Keep it under five lines. This is a handoff to future-you, not journaling for its own sake.
Step 4: Ask for Feedback on the Output, Not the Intention
Request comments on the artifact—the memo, deck, or decision log—not on whether you “seemed more strategic.” Ask one question: “What would make this more useful next time?” Feedback on real work transfers faster than personality praise.
Step 5: Promote the Pattern Into the Next Assignment
After two or three cycles on similar work, raise the difficulty slightly: larger audience, tighter deadline, messier stakeholders. That is your progression path. No competency matrix required.
What to Stop Doing
Stop collecting skill checklists you will not use this quarter. Stop treating formal training as proof of growth. Stop waiting for a manager-built plan before you practice. Your calendar already holds the curriculum if you treat projects as practice fields.
Start This Week
Open your task list. Circle one deliverable. Write the one-sentence stretch. Redesign one step so the skill is unavoidable. Ship, note, and ask one feedback question. That is professional development that shows up in the work itself—not in a folder of unfinished courses.
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 kendell for more practical guidance.
Related Resources
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.