Personal Effectiveness
Executive view
Evaluate practitioners on reusable assets and decision quality over time, not hours logged. Ask: What patterns did they leave the firm or client? How do they prioritise in ambiguity?
Decision required: Is this person building career compound interest—or starting from zero each quarter?
Technical view
Implement weekly priority cards, decision journals, pattern notes, and learning backlogs tied to Learning Map topics. Protect **90–120 min** deep work blocks minimum four days per week.
Link growth goals to [Career and capability roadmap](/ai-solution-engineering/career-roadmap) competencies explicitly.
Why this matters
AI Solution Engineering is breadth-heavy: business, ML, architecture, security, commercial, ops, leadership. The field changes faster than any single engagement cycle. Practitioners who rely on memory and hustle hit a ceiling:
- Every RFP starts from zero—win rate stagnates
- Eval mistakes repeat because last project's eval note was lost
- Calendar owns them—no time to read papers or update skills
- Decisions are forgotten—same architecture argument every year
- Burnout ends careers early in a high-demand market
Personal effectiveness is not productivity theatre—colour-coded Notion with 47 tags. It is minimum viable systems that:
- Preserve deep work for hard problems (eval design, architecture, decision memos)
- File patterns after each engagement (problem, architecture, failure mode, metric)
- Improve judgment via decision journal reviews
- Direct learning via backlog linked to map topics
- Manage energy—not only time—so ethics and leadership work remain sustainable
Topic 35 closes the Learning Map before the Competency test—systems prove you integrated the curriculum into practice.
Learn
Time systems — calendar as strategy
Principles:
- Plan week before it plans you — Friday or Sunday 30-min review
- Time-block deep work — same slot daily; treat as client meeting
- Batch shallow work — email, Slack, expenses 2× daily max
- Buffer 40% on engagement estimates — AI unknowns are real
- Say no with alternative—protect focus without burning bridges
Weekly priority card (one page):
| Element | Content |
|---|---|
| 3 outcomes | Must finish this week (client-visible) |
| 2 deep work blocks | Topic or artefact (eval spec, ADR) |
| 1 learning item | From learning backlog |
| 1 relationship | Sponsor, mentor, peer review |
| Stop doing | One thing to drop or delegate |
Review Friday: done / deferred / learned.
Deep work — Cal Newport adapted for AI engineers
Deep work-worthy tasks:
- Eval harness design and error analysis
- Architecture decision memos
- Threat modelling and abuse cases
- RFP acceptance annex drafting
- Reading papers or reference-depth map topics
Not deep work: status email, passive webinar, reorganising folders.
Minimum: 90 minutes × 4 days/week uninterrupted—phone away, Slack paused.
Shutdown ritual: End day with 5-min note—tomorrow's first deep task, open loops captured—reduces night anxiety.
Energy management — not only hours
Energy drains in AI roles:
- Context-switching between client A banking and client B pharma same day
- Moral stress from ethics pressure without escalation path
- On-call plus daytime workshops
- Novelty overload—every week new model announcement
Replenish:
- Sleep non-negotiable baseline
- Exercise and movement between virtual meetings
- One news/model feed—not twelve
- Recovery blocks after launch weeks
- Therapy or coaching where appropriate—leadership is emotional labour
Track energy 1–5 daily in journal one week—spot patterns.
Decision journal — improve judgment
After significant decisions (architecture, hire, escalate, scope cut):
Date:
Decision:
Context (3 sentences):
Options considered:
Criteria:
Expected outcome:
Confidence (1–10):
Review date:
---
Actual outcome (fill later):
Lesson:
Quarterly review: Where were you overconfident? Systematic bias (speed over security)?
Pairs with topic 33 decision memos—journal is personal; memo is organisational.
Pattern library — engagement IP
One-page pattern template:
Title: [e.g. Regulated RAG with citation gate]
Problem type:
Industry / context:
Architecture sketch (text or link):
Key eval metrics:
Failure modes seen:
Mitigations that worked:
Commercial note (TCO order of magnitude):
Stakeholder lesson:
Source engagement (confidentiality-safe):
Date:
Tags: #RAG #banking #eval
Store in searchable tool—Notion, Obsidian, git repo, SharePoint.
Rule: Within 5 business days of engagement end or phase gate, file one pattern minimum.
Learning loops — map to practice
Learning backlog item format:
| Field | Example |
|---|---|
| Topic | 21 Eval QA |
| Gap trigger | Faithfulness drop undetected 2 weeks |
| Resource | Map topic 21 + eval cookbook |
| Practice exercise | Design abstention set for HR copilot |
| Done when | Exercise filed in pattern library |
| Target date |
Link backlog to Career and capability roadmap—next role needs which topics deepened?
Spaced revisit: Review map topic notes at 30/90 days—retention beats one-time read.
Templates and reuse — proposal acceleration
Maintain sanitized templates:
- Discovery question bank
- Stakeholder map shell
- Eval plan outline
- ORR checklist excerpt
- Decision memo and ADR shells
- Impact note skeleton
- Weekly status BLUF
Version control templates—date in footer; changelog when eval standards shift.
Never copy client-confidential text into templates—rebuild from pattern structure.
Meeting and communication discipline
- Agenda required for meetings you accept
- BLUF in first two sentences of email to executives
- Pre-read 48h before steering—you own sending it if organiser forgets
- No meeting without Decide or action outcome defined
- Notes within 24h—decisions and owners
Pairs with topic 28; personal discipline makes communication topic usable.
Writing and speaking — craft compounds
- One page max for exec decision unless asked
- Active voice; numbers beat adjectives
- Practice tech talk once aloud—catch jargon
- Post-mortem blog internally (confidentiality cleared)—teaches others, cements learning
Resilience and boundaries
- Vacation with handover—not heroic laptop on beach
- Escalate ethical stress—carry alone leads to cynicism
- Peer group outside project—sanity check
- Saying no to scope creep protects client outcome too
Notes systems — capture to retrieve
Progressive summarisation:
- Capture raw notes (meeting, reading)
- Bold key points same day
- Summarise top 3 in pattern or journal within week
- Link to project or tag
Avoid collectors fallacy—500 saved papers unread. One applied concept beats ten bookmarked.
Frameworks and methods
PARA for engagement materials
Projects — active client folders
Areas — ongoing responsibilities (skills, health)
Resources — patterns, templates, papers
Archive — closed engagements indexed
Move project artefacts to Resources as patterns at close.
Eisenhower for weekly triage
| Urgent | Not urgent | |
|---|---|---|
| Important | Do now (incident) | Deep work schedule |
| Not important | Delegate/batch | Eliminate |
AI engineers live in urgent-not-important (Slack)—weekly review pulls important-not-urgent (eval design) into calendar.
OKRs personal — quarterly
Objective: Become credible lead for regulated RAG
KRs: 3 patterns filed; topic 21 exercise done; one client steerco presentation
Align OKRs to Career and capability roadmap.
Annual learning plan
| Quarter | Focus topics | Output |
|---|---|---|
| Q1 | 13 RAG, 21 eval | Eval pattern |
| Q2 | 30–31 commercial | Acceptance template |
| Q3 | 33 leadership | Decision memo portfolio |
| Q4 | 32 ops | Runbook pattern |
Adjust to role—EM weights 33 higher; architect weights 8–15.
Engagement close ritual — 90 minutes
- Pattern note (60 min)
- Decision journal entries for top 3 decisions (15 min)
- Learning backlog update (10 min)
- Template improvements from friction list (5 min)
Non-optional before starting next major engagement.
Anti-patterns catalogue
| Anti-pattern | Fix |
|---|---|
| Blank page every pitch | Pattern library search first |
| Read map, no exercise | Every topic → one filed artefact |
| Infinite news scrolling | One digest; deep dive scheduled |
| Hero weeks then crash | Energy boundaries; sustainable pace |
| Notes scattered | PARA + weekly tidy 15 min |
Real-world scenarios
Scenario A — Consultant: pattern library wins RFP
Context: Senior consultant; third FS copilot RFP in 18 months; previously 3 weeks proposal prep each time.
System: 12 patterns tagged #RAG #banking; acceptance annex template; eval metric table.
Outcome: RFP response 6 days; reused architecture 70%; won £1.4m phase—partner cites "specificity of acceptance language."
Numbers: Prep cost ~£9k internal vs ~£28k prior average; win rate 2/3 vs 1/3 before library discipline.
Scenario B — IC: deep work recovery
Context: Platform engineer; 14 meetings/week; eval debt; faithfulness incident client-visible.
Intervention:
- Weekly priority card—two outcomes: eval suite fix, runbook update
- Deep work 7:00–9:00 daily; Slack off
- Declined 3 optional meetings with polite redirect
- Decision journal on "defer eval to post-launch" mistake
Outcome: Eval automated weekly; incident repeat risk down; promotion case cites operational discipline.
Numbers: Deep work hours 4 → 11/week; eval lag 14 days → 2 days.
Scenario C — EM: learning loop for new domain
Context: Engineering manager first pharma engagement; MLR constraints foreign.
Learning backlog:
- Topic 18 privacy + topic 19 governance — 2 weeks
- Shadow MLR meeting — 1 day
- Practice impact note — filed
Outcome: Avoided autonomous send design error; saved ~$600k rework estimate from similar case study in pattern library.
Scenario D — Burnout prevention
Context: Lead; 4 months consecutive travel; ethics tension on dual-use client; sleep 5h average.
Systems change:
- Hard stop one client off rotation
- Therapy via firm EAP
- Energy tracking—reduced evening email
- Delegated decision memos to senior with review
Outcome: Retained role; team decision velocity +20% as lead stopped being bottleneck.
Numbers: Attrition risk self-assessed 8/10 → 4/10 in 8 weeks; no programme quality drop.
Template index — personal effectiveness starter kit
| Template | Filename | Source topic |
|---|---|---|
| Weekly priority card | weekly-priority.md | 35 |
| Decision journal entry | decision-YYYY-MM-DD.md | 35 |
| Pattern note | pattern-[slug].md | 35 |
| Decision memo | decision-memo.md | 33 |
| MEAT acceptance | acceptance-annex.md | 30 |
| Eval plan outline | eval-plan.md | 21 |
| Impact note | impact-note.md | 34 |
| ORR excerpt | orr-checklist.md | 32 |
Store in ~/playbook-templates/ or team repo—version in README.
Learning map study schedule — 35-topic completion path
| Phase | Topics | Weeks (part-time) |
|---|---|---|
| Foundation | 1–10 | 10 |
| Architecture | 11–16 | 6 |
| Trust | 17–21 | 5 |
| Commercial | 22–32 | 8 |
| Leadership | 33–35 | 3 |
32 weeks at ~3–4 hours/week—adjust; topic 35 systems make subsequent passes faster.
Spaced repetition for technical retention
After completing a topic:
- Day 1: Primary exercise
- Day 7: Teach-back to peer 5 min
- Day 30: Re-run one practice question cold
- Day 90: Apply pattern on engagement
Without spacing, reference-depth read fades—exercises matter.
Career evidence log — promotion packet input
| Quarter | Artefact | Competency |
|---|---|---|
| Q1 | Won RFP using pattern library | Commercial |
| Q2 | Led eval recovery incident | Ops + leadership |
| Q3 | Ethics impact note adopted | Governance |
| Q4 | Mentored 2 engineers on map | People |
Review with manager against Career and capability roadmap.
Context-switching cost — measurement week
Log switches one week:
- Client changes count
- Productivity self-score 1–5 each afternoon
- Deep work minutes
If switches >8/day and deep work <6h/week, renegotiate allocation with engagement lead—data beats complaint.
Reading vs doing ratio
Target 1:1 for map study—each hour read, one hour exercise.
For topic 35 itself: building systems is the exercise—meta but required.
Practice exercises
Primary exercise — Personal learning backlog (45 minutes)
Tasks:
- List five gaps from Learning Map topics 1–35 (honest self-assessment).
- For each: resource (map topic), practice exercise, done-when, target date next 90 days.
- Pick one to complete this week—schedule deep work block.
- Create weekly priority card for current week (real or simulated).
- Write one decision journal entry for recent decision.
Acceptance criteria:
- Exercises are specific—not "learn RAG"
- At least one item links to Career and capability roadmap
- Priority card has stop-doing line
Stretch exercise — Pattern library bootstrap (half day)
Tasks:
- Create pattern template in your tool of choice.
- Write three patterns from past engagements (anonymised)—or three realistic composites from map scenarios.
- Extract two templates from patterns (eval outline, decision memo shell).
- Document engagement close ritual in calendar recurring.
- Quarterly OKR personal draft aligned to next career step.
- PARA folder structure for current work.
Acceptance criteria:
- Patterns searchable by tag
- Each pattern includes failure mode and metric
- Close ritual scheduled before next engagement start
Scenario G — Sabbatical and pattern library continuity
Context: Lead takes 3-month sabbatical; no patterns filed prior; team reinvents eval approach; £40k wasted.
Prevention:
- Mandatory pattern handoff meeting 2 weeks before leave
- Deputy owns template repo
- Auto-reminder: engagement close ritual assigns deputy filer
Personal effectiveness includes organisational continuity—not solo hero knowledge.
Scenario H — AI news FOMO management
Context: Engineer spends 10h/week on X/LinkedIn model launches; delivery slips.
System:
- One curated digest Friday 30 min
- Learning backlog captures "investigate X" with date—not instant rabbit hole
- Deep dive only if client impact in 30 days
Protects deep work while staying current.
Personal effectiveness maturity model
| Level | Behaviour |
|---|---|
| 1 | Reactive; no patterns |
| 2 | Some templates; inconsistent |
| 3 | Weekly priorities; pattern library started |
| 4 | Decision journal + learning backlog habit |
| 5 | Teaches others; compounds firm IP |
Target level 4 before senior/principal credential; level 5 for distinguished path per Career and capability roadmap.
FAQ — personal effectiveness
Q: Minimum viable pattern library size?
A: One pattern per engagement; 12+ patterns = noticeable proposal acceleration for most consultants.
Q: How long to build habit?
A: Weekly priority card ~8 weeks; decision journal ~12 weeks—use calendar reminders until automatic.
Q: Deep work when calendar insane?
A: Protect 2 blocks/week minimum; negotiate with lead; 90 min beats zero; batch meetings to two days if possible.
Q: Decision journal vs ADR?
A: ADR = team architecture record; journal = personal judgment improvement—including non-architecture decisions.
Q: When update career roadmap link?
A: Quarterly with manager or self-review—map competencies to gaps in learning backlog.
Sample weekly priority card (filled example)
Week of 28 Jul 2026
Outcomes: (1) Finish faithfulness runbook draft; (2) Client steerco pack BLUF; (3) Pattern file #retail-RAG-eval
Deep work: Tue 7–9 eval runbook; Thu 7–9 steerco pre-read
Learning: Topic 32 stretch ORR exercise — Fri lunch
Relationship: 1:1 with DE lead on corpus gate
Stop doing: Optional vendor bake-off demo prep (delegate to architect)
Pattern library entry skeleton (copy-paste)
# Pattern: [Title]
## Problem
## Context / industry
## Architecture
## Eval metrics
## Failure modes
## Mitigations
## Commercial (order of magnitude)
## Stakeholder note
## Tags
## Date
Fill within 5 business days of phase end.
Annual personal retrospective template
Year: ______
Top 3 delivered outcomes:
Top 3 patterns filed:
Best decision (journal):
Worst decision (lesson):
Learning map topics deepened:
Career roadmap progress:
Energy average (1–5):
Next year OKRs:
Complete between Christmas and New Year—2 hours—feeds performance conversation.
Integration with engagement management
Share non-confidential patterns with practice lead (permission permitting)—multiplies firm effectiveness beyond personal library.
Redact client identifiers; focus problem class and architecture—feeds community of practice.
Time audit — one week diagnostic
Track in 15-min blocks:
- Client delivery
- Internal meetings
- Learning
- Admin
- Sales/support
If delivery <50% on billable engagement, escalate workload with data—not vague "too busy."
Decision journal — three example entries (composite)
Entry 1 — Scope: Accepted CR to add second language without eval budget. Outcome: Bad. Lesson: No language without eval line in SOW.
Entry 2 — Architecture: Chose private deployment over SaaS despite cost. Outcome: Good—CISO sign-off smooth. Lesson: Security time saved > licence delta.
Entry 3 — Personal: Skipped weekly review 4 weeks during crunch. Outcome: Missed pattern filing; repeated mistake on next engagement. Lesson: Minimum viable review non-negotiable.
Review quarterly—patterns in your own judgment emerge.
Learning backlog — five example items (filled)
| Topic | Gap | Exercise | Done when |
|---|---|---|---|
| 21 Eval | Abstention set weak | Build 50-query abstention set | Filed in pattern library |
| 30 Contract | Weak acceptance language | MEAT annex for practice RFP | Peer review pass |
| 33 Leadership | Avoid conflict | Decision memo on live deadlock | Memo in wiki |
| 34 Ethics | No carbon estimate | Routing comparison memo | Attached to impact note |
| 35 Patterns | Library empty | 3 patterns from past projects | Searchable tags live |
Copy structure for primary exercise—personalise gaps honestly.
Scenario I — Pattern library on second engagement
Context: Same consultant; banking RFP #2; opens pattern #banking-RAG-acceptance-v1; adapts thresholds 90 min vs 2 weeks first time.
Outcome: Higher quality submission; partner delegates more RFPs; career trajectory accelerates per Career and capability roadmap.
Numbers: Win rate 50% → 67% on small sample; 120 hours/year saved—reinvested in topic 21 eval depth.
Scenario J — Burnout recovery via systems reset
Context: Principal IC; 6 months no patterns; decision journal empty; competency test deferred twice.
Reset week: Block calendar; file 3 retrospective patterns; restart weekly card; one learning backlog item completed; manager alignment on sustainable load.
Outcome: Competency test passed month 2 post-reset; engagement NPS stable.
Systems recovery is faster than skill relearning from scratch.
Deep work environment checklist
- Phone in another room or DND
- Slack status Deep work — urgent only
- Single task on screen (close tabs)
- Water/coffee before block—no mid-block kitchen trip
- Calendar declined for overlapping invites
- Output defined ("draft runbook section 3" not "work on ops")
Use checklist first 2 weeks until habit forms.
Pattern library search workflow (before any new deck)
- Search tags: industry + pattern type
- If hit ≥1: fork pattern; update metrics
- If miss: plan new pattern at engagement end
- Never start executive summary before step 1
60-second discipline saves hours.
Competency test week preparation schedule
| Day | Activity |
|---|---|
| −7 | Gap list from learning backlog |
| −5 | Re-run 3 cold questions per weak topic |
| −3 | Peer quiz 30 min |
| −1 | Rest; light pattern review only |
| Test | Artefacts mentally indexed—not cramming |
Topic 35 systems make preparation distributed—not cram week panic.
Personal OKR example — Principal AI Solution Engineer
Objective: Establish recognised eval + commercial expertise in FS sector.
KR1: File 6 FS-tagged patterns in library by Q4.
KR2: Lead 2 client steercos with documented decision memos.
KR3: Pass competency test with ≥85%.
KR4: Mentor 1 engineer through topics 21 and 30 exercises.
Review quarterly against Career and capability roadmap.
Note-taking during reference-depth study
For each map topic: one page max personal summary—not copy-paste. Sections: when to use, top 3 artefacts, one scenario number I remember, one question I still miss. File in learning-map-notes/. Makes competency test revision 30 min per stage not re-read 5500 words.
Engagement travel effectiveness
- Flight time: one decision journal backlog review or pattern outline
- Hotel evening: not client work unless Sev1—protect sleep
- Jet lag weeks: reduce deep work targets 50% on priority card—honest capacity
Travel without adjusted systems causes pattern library drought—schedule close ritual before heavy travel month.
Weekly review — filled retrospective example
Week 28 Jul 2026: Outcomes 2/3 (runbook done; steerco done; pattern deferred → Monday). Deep work 9h (target 8h). Learning: completed topic 32 primary exercise. Lesson: defer pattern same-day next time. Next week: pattern #retail-RAG, topic 34 impact note draft, protect Tue/Thu AM blocks.
Honest retros—not performative 3/3 every week—build self-trust in capacity planning.
Template versioning discipline
When eval standards or MEAT language improves, bump template v1.0 → v1.1 with changelog line in README. Proposals cite template version in footer—audit trail when client asks why acceptance language changed year over year.
Closing the Learning Map — integration checklist
- Topics 30–35 exercises filed in pattern library
- Stage 6 exit checklist complete
- Competency test scheduled
- Personal OKR aligned to Career and capability roadmap
- One teach-back session delivered to peer or mentee
Topic 35 is the capstone habit layer—systems that let you retain and apply all prior thirty-four topics across engagements.
Morning startup routine (10 minutes)
- Read yesterday's shutdown note
- Update one line on weekly priority card
- Confirm today's deep work block still protected
- Scan calendar for meetings without agenda—decline or request
Small ritual prevents reactive day before it starts.
Evening shutdown routine (5 minutes)
- Log one decision journal stub if decision made
- Note tomorrow's first deep task
- Close laptop—signal end to household/self
Borrowed from Cal Newport; adapted for consulting travel variability.
Pattern library metrics — track quarterly
| Metric | Target |
|---|---|
| Patterns filed | ≥3/quarter |
| Pattern reuse events | ≥2/quarter |
| Template version bumps | ≥1/quarter when learning |
| Hours saved (estimated) | Log in retrospective |
Quantifying reuse motivates maintenance when library grows past 20 entries—otherwise search rot sets in.
Handoff to competency test
When topics 1–35 complete and Stage 6 exit checklist signed, schedule Competency test within 14 days while patterns and decision journals are fresh—delayed tests correlate with map tourism without retention. Treat the test as evidence of systems working, not a separate cram event. Your pattern library and decision journal are the study materials—if they are empty, return to topic 35 exercises before booking the test slot.
Questions you should be able to answer
- What are my three outcomes this week—and what did I stop doing?
- When is my daily deep work block—and is it protected?
- What did I file in my pattern library last month?
- What decision did I journal—and what review date is set?
- What is on my learning backlog for the next 90 days?
- Which Learning Map topic gap caused my last rework?
- What template saved me time recently—or should have existed?
- How is my energy 1–5 this week—and what drained it?
- What OKR or career roadmap competency am I building this quarter?
- What is my engagement close ritual—and did I run it last time?
- Where do notes live—and can I find last steerco decision in 2 min?
- How many meetings could be async this week?
- What news or learning input is curated vs chaotic?
- Who is my peer sanity-check outside the project?
- What pattern will I reuse on the next similar opportunity?
Pattern library taxonomy — suggested tags
Organise for search at scale:
Domain: #banking #pharma #public-sector #retail #manufacturing
Pattern type: #RAG #agent #eval #FinOps #contracting #ops #leadership
Outcome: #won-RFP #incident-learned #pilot-only
Risk tier: #tier-low #tier-medium #tier-high
Review tags quarterly—merge duplicates.
Decision journal — quarterly review worksheet
Every quarter, read last 10 entries:
- Where was confidence >7 but outcome poor? (overconfidence bias)
- Where did I defer decision too long? (avoidance)
- Which criteria repeated? (update personal checklist)
- One system change (template, ritual, delegate rule)
File summary in pattern library #meta-learning.
Deep work defence — organisational tactics
When calendar culture fights blocks:
- Shared team focus mornings—meetings banned 9–11
- Office hours instead of ad hoc pings
- Async video updates replace status meetings
- Executive cover—sponsor email endorsing focus time for eval work pre-launch
Personal tactics insufficient alone on matrixed programmes—negotiate team norms.
Competency test preparation — evidence portfolio
Before Competency test, assemble:
| Evidence | Source topic |
|---|---|
| Architecture ADR | 8, 15 |
| Eval plan | 21 |
| Impact note | 34 |
| Decision memo | 33 |
| Pattern library 5+ entries | 35 |
| Commercial model snippet | 07, 22 |
Map each to test rubric—study gaps only.
Mentoring others on the Learning Map — lead practice
Senior practitioners teach the map:
- Assign mentee one topic/month with primary exercise
- Review artefact in 30-min session
- Mentee presents 15-min teach-back to squad
Doubles learning—mentor refreshes Stage 1–4 basics.
Tooling choices — minimal stack
Avoid productivity procrastination:
| Need | Minimal tool |
|---|---|
| Patterns | One wiki or Obsidian vault |
| Decisions | Markdown files dated |
| Priorities | Paper or single doc |
| Learning backlog | Table in same vault |
| Templates | /templates folder in git |
One stack maintained beats three abandoned apps.
Scenario E — Pattern reuse on compressed timeline
Context: 2-week RFP response; new industry (energy); lead has #RAG #eval patterns only.
Action: Compose from three patterns—acceptance annex, eval plan, stakeholder map—60% net new industry research.
Outcome: Credible submission; shortlisted; partner handles domain SME gap.
Numbers: 80 hours effort vs 200 without patterns; win probability model improved +25% vs no-bid.
Scenario F — Decision journal prevents repeat mistake
Context: Journal entry 6 months prior: "Accepted client push to skip retrieval eval—faithfulness risk."
New client similar push; lead reads journal on Sunday planning; insists eval gate; avoids repeat incident.
Lesson: Journal is organisational memory when teams rotate.
Weekly review script — 30 minutes Friday
- Priority card score (3 outcomes met?)
- One win / one miss / one lesson
- Pattern or journal update queued
- Next week deep work blocks scheduled
- One no to prepare for Monday
Print script until habit—12 weeks to automaticity research suggests.
Integration with firm performance cycle
Align personal OKRs to annual review:
- Patterns contributed: target 6/year
- Learning map topics deepened: target 4/year with exercises
- Mentoring hours: firm policy
Evidence makes review ** factual**—not recency bias.
Health and sustainability of knowledge work
Long AI careers require:
- Vacation without laptop—true disconnect
- Skill refresh budget—conference or course 1×/year
- Peer community—internal guild or external meetup
- Boundaries on ethics stress—escalate, do not absorb alone
Personal effectiveness includes staying in the profession decade two.
Extended Learn — atomic habits for consultants
Stack habits:
- After morning coffee → 5 min priority card
- After client call → 3 bullet decision journal stub
- After steerco → one pattern tag filed Friday batch
- Before weekend → weekly review 30 min
Small hooks beat annual resolution.
Extended Learn — saying no scripts
| Request | Script |
|---|---|
| Extra scope | "Happy to—suggest CR or defer X; which priority?" |
| Meeting without agenda | "Send agenda and I'll confirm fit." |
| Weekend deploy | "Tier-high needs CAB; earliest Monday unless Sev 1." |
| Skip eval | "Acceptance requires eval; which threshold should we waive in writing?" |
Politeness + criteria preserves relationships.
Extended Learn — building a second brain without overwhelm
Capture → Organise (PARA) → Distill (pattern) → Express (proposal, blog, teach).
Skip express step = hoarding; skip distil = noise.
Aim one express output per month minimum—internal brown bag counts.
Extended Learn — financial effectiveness for contractors and FTE
Track effective hourly rate after learning investment:
- Billable hours vs admin
- Win rate improvement from patterns
- Promotion or rate increase evidence
Personal effectiveness has economic dimension—especially professional services.
Extended Learn — peer learning circles
Form 3–4 person map study group:
- Weekly 45 min—one person teaches topic exercise solution
- Rotate scribe for shared pattern notes
- Accountability for competency test date
Social learning increases completion 2–3× vs solo.
Extended Learn — when to break your own systems
Systems serve outcomes—break glass when:
- Sev 1 incident—all hands, skip deep work block
- Client crisis—short sprint, then recovery day scheduled
- Family emergency—no guilt; journal "interrupted week" and resume
Resilience includes flexibility, not rigid dogma.
Negative cases — when personal effectiveness fails
Blank page every time
Symptom: No pattern library; reinvention; slow proposals.
Impact: Lower win rate; senior plateau.
Fix: Close ritual; one pattern per engagement minimum.
Map tourism
Symptom: Read 35 topics; zero exercises filed.
Impact: False confidence; competency test fail.
Fix: Learning backlog with done-when artefacts.
Calendar anarchy
Symptom: No deep work; eval debt; reactive quality.
Impact: Incidents; burnout.
Fix: Priority card; time blocks; meeting decline discipline.
Decision amnesia
Symptom: Same debate quarterly; no journal.
Impact: Team distrust; slow architecture.
Fix: Decision journal + ADR habit.
Collector not practitioner
Symptom: 200 bookmarks; no applied eval improvement.
Impact: Stagnant skills as models shift.
Fix: One applied exercise per learning item.
Burnout heroics
Symptom: Pride in unsustainable weeks; crash post-launch.
Impact: Exit industry; team loses leader.
Fix: Energy tracking; boundaries; delegation topic 33.
Practice checklist
- I use a weekly priority card with three outcomes
- I protected at least four deep work blocks this week
- I filed or updated one pattern library entry
- I wrote one decision journal entry with review date
- My learning backlog has five items with done-when criteria
- I linked one growth goal to career roadmap
- I scheduled engagement close ritual for current/next engagement
Related playbook content
- Career and capability roadmap — Role progression and competency evidence
- How to use this Learning Map — Reference-depth study method
- Competency test — Capstone after topic 35
- Leadership and People Management — Delegation and energy of teams
- Communication and Executive Articulation — BLUF and exec writing
- Presales and Solution Shaping — Reuse patterns in proposals
- Leadership — Stage hub and exit criteria
- Build Future Capability roadmap — Firm future skills
- Leadership: Build Future Capability Before It Is Urgently Needed — Long-horizon learning
- 8D Framework — Lifecycle pattern sources
Discussion
Comments
Share feedback or questions about this page. No account required.
Loading comments…