From career knowledge to reusable evidence
Interview preparation became a reusable workflow grounded in Portfolio evidence, with real opportunity runs showing that output validation matters beyond implementation.
This week’s focus
The career-projection work started with preparation for specific AI leadership and architecture conversations, but exposed a broader constraint: the evidence needed to prepare was already captured in the Portfolio, yet each opportunity risked recreating the same preparation work. The question became how to operationalise that knowledge without weakening its grounding in actual experience.
What actually happened
- Preparation for AI CoE and Head of AI & Automation conversations evolved from a one-off interview package into a reusable Master Interview Playbook generator.
- Portfolio knowledge became the evidence source for opportunity-specific preparation rather than manually reproducing career context for each run.
- The workflow separated opportunity interpretation, evidence retrieval, experience matching, and interview preparation across specialised responsibilities.
- Implementation was followed by execution and output review, with observed deficiencies converted into refinement requirements and subsequent reruns.
- The generator was exercised against real opportunities, including an AI CoE Enterprise Architecture scenario and an Enterprise Governance Architect contract whose corrected five-day commitment materially changed its commercial assessment.
Key trade-offs
- Reusing Portfolio knowledge reduced repeated preparation, but required tighter evidence boundaries to prevent generated positioning from exceeding actual experience.
- Specialising workflow responsibilities increased orchestration and hand-offs, but made retrieval, matching, and synthesis independently inspectable.
- Using real opportunities for validation required repeated human review, but exposed issues that implementation summaries alone could not demonstrate.
What changed in my thinking
- Career knowledge becomes more useful when it can operate as source evidence for repeatable workflows rather than remaining static documentation.
- Reviewing actual generator runs reframed implementation completion as an intermediate milestone; the meaningful validation point is whether the resulting preparation accurately represents the evidence and opportunity.
- The contract assessment showed that career projection cannot rely on capability fit alone: corrected engagement terms changed the opportunity assessment despite the role remaining professionally relevant.
Architecture signals
- Treat authoritative knowledge as source evidence rather than regenerating context for each execution.
- Separate evidence retrieval from interpretation and articulation.
- Validate generated workflows through observable outputs, not implementation completion.
- Re-evaluate outputs when material source inputs change.
Key takeaways
- Reusable preparation starts with reusable evidence, not reusable answers.
- Grounding boundaries matter when generated outputs represent real experience.
- Successful implementation does not establish successful workflow behaviour.
- Real-world inputs provide stronger validation than synthetic scenarios alone.
Assumptions invalidated
- Career context needed to be manually assembled for each opportunity; existing Portfolio knowledge could serve as reusable workflow evidence.
- Completing the specified implementation meant the generator was ready; execution reviews exposed further refinement needs.
- Professional relevance was sufficient to make an opportunity viable; corrected commercial terms materially changed the assessment.
System evolution
- Career preparation shifted from one-off content generation to a sequential evidence-grounded workflow using reusable knowledge and specialised responsibilities.
- Portfolio content shifted from static career documentation to an operational evidence source for career projection.
- Validation shifted from implementation review to an iterative execution → output review → refinement → rerun loop.
Looking ahead
The next question is how reliably the workflow can project the same evidence across materially different opportunities without overfitting preparation to a particular role. Continued real-world use can clarify which evidence and evaluation boundaries need to remain explicit as the generator evolves.
⸻
Related Experiments
Note:
- This Weekly Learning was produced using the Ideas to Life Weekly Learning system map