Home› Groups› APHRC’s Interns› Private: APHRC’s Interns› Revisiting: From Internship to Opportunity: Stories of Growth…

Revisiting: From Internship to Opportunity: Stories of Growth and Progression

Started by Rhoda Nakhosi Sep 16, 2026 7 replies 👁 8 views
Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
Sep 16, 2026 at 9:34 pm (edited)

This thread is worth revisiting. The point that Kevin has said about consistency over comparison is one that bears repeating, especially for those still in the early stage.

Wherever you are now, still interning, in a temporary role, or settled into something permanent , your journey has something in it that someone else needs to hear. Not the polished version. The real one: what you learned, what surprised you, what you would do differently.

So if you have not shared yet: what has your path looked like since your internship? What is one lesson you would pass on?

Picking up an earlier discussionFrom Internship to Opportunity: Stories of Growth and Progression, last active May 2026.

Nonvicks Ochieng Member Community Champion (1,500+ points) Community Champion
5 days ago

@Rhoda Nakhosi Thanks for bringing this up. This is my approach to the questions. 

  Building Beyond the Assigned Scope: Real growth usually happens when taking ownership of projects slightly outside the original job description. Moving from intern to full-time contributor usually hinges on demonstrating initiative without waiting to be asked.

Core Lessons to Pass On

  1. Optimize for Learning Velocity Over Title: Early in a career, the rate at which you learn, get feedback, and adapt matters far more than the exact title on your contract or how your progress compares to peers.

  2. Document Your Mistakes, Not Just Victories: Keepsakes of what went wrong—and how you resolved it—are infinitely more valuable for long-term growth than a list of easy wins.

  3. Consistency Outlasts Intensity: Daily, reliable execution builds trust faster than sporadic bursts of high performance. Show up, deliver steadily, and focus on your own timeline.

Michelle Shiroya Member Contributor (50+ points) Contributor
↩ replied to Nonvicks Ochieng 2 days ago

Nonvicks Ochieng wrote:
Document Your Mistakes, Not Just Victories: Keepsakes of what went wrong—and how you resolved it—are infinitely more valuable for long-term growth than a list of easy wins.

I really like this point, its through mistakes that you will grow and learn and sharpen your expertise in your area or specialization. And in as much as wins are great to keep record of, its in the mistakes that you get to refine your thinking and build on your experience

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Michelle Shiroya 1 day ago
@Michelle Wanguku Shiroya, you put your finger on something important. Wins tell you what worked once; mistakes tell you what you're made of when things don't go to plan. That refinement you mentioned is real and I would add that mistakes also teach you which feedback is worth keeping and which is just noise. I have found that the mistakes I resisted the most at the time are the ones I quote to myself years later. The wins are nice for the CV; the mistakes are what actually built the judgment. So, a question back to you: what's one early career mistake you're now grateful for? The one that stung but ended up pointing you somewhere better.
Nonvicks Ochieng Member Community Champion (1,500+ points) Community Champion
↩ replied to Michelle Shiroya 1 day ago

@Michelle Shiroya Excellently put. Refining your thinking through problem-solving is what turns basic knowledge into true expertise!

A lot of people naturally shy away from recording mistakes out of fear or discomfort, so viewing them as 'keepsakes for growth' is a huge mindset shift.

Curious to hear: how do you usually capture those reflections do you keep a personal journal, a running doc, or do quick post-project debriefs?

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Nonvicks Ochieng 1 day ago
@Nonvicks Ochieng, "Optimize for learning velocity over title" is the line I wish someone had told me earlier. It's tempting in the early stage to measure yourself against whoever got promoted first, but that comparison often hides how much of it was timing, luck, or simply being in the right room. Your point about documenting mistakes really landed for me. I have started keeping a running "what went wrong and why" note, and rereading it months later is equal parts humbling and clarifying. The wins rarely teach you anything new but the mistakes almost always do. When you say "read more," what's the one mistake from your own early career that you're now grateful for? The one that stung at the time but redirected you somewhere better.
Nonvicks Ochieng Member Community Champion (1,500+ points) Community Champion
↩ replied to Rhoda Nakhosi 1 day ago

@Rhoda Nakhosi Seeing your growth through that running note is amazing. That humble reflection is exactly what builds long-term expertise.

The sting that redirected me early on was working in a silo for weeks on a complex deliverable without checking in, assuming I had to present a 'perfect' finished product. When I finally shared it, half my assumptions were wrong because the project context had shifted days earlier. It felt terrible to scrap so much work.

That painful moment forced me to adopt an 'async and early feedback' mindset. I stopped waiting for perfection and started sharing rough drafts and asking quick questions early on. It built trust much faster, saved endless hours, and taught me that iteration beats isolated perfection every single time.

Rhoda Nakhosi Admin Community Champion (1,500+ points) Community Champion
↩ replied to Nonvicks Ochieng 1 day ago
@Nonvicks Ochieng, the silo story hits close to home. I did something similar early on: spent days polishing a report nobody had asked for in that format, because I assumed "good work speaks for itself." It didn't. What I learned is that perfectionism in isolation isn't diligence, it's a form of hiding. You avoid the vulnerability of showing unfinished work, but you also avoid the correction that would have made it right.
Your "async and early feedback" shift is the real unlock. I'd add one nuance: it only works if the people around you have made it safe to share rough drafts. Some environments punish early honesty and reward late polish. So part of the lesson is also choosing or helping build a culture where "here's my messy first pass" is met with curiosity rather than judgment.
That's actually something I'd love to hear from others here @Shamim Kowa Talla @guest586@aphrc.org @all: How do you signal to your team that half-baked ideas are welcome? Because I suspect many early-career folks know they should ask for feedback sooner, but they don't feel safe doing it yet.