AI Skill Report Card
Building Expert Personal Brand
Quick Start14 / 15
Pick the format that fits the goal:
- Talk/presentation → use the Talk Workflow below, output a structured outline + slide skeleton.
- Expert article → use the Article Workflow below, output a publication-ready draft.
Both share the same core move: start from a sharp, narrow claim backed by real experience, not a broad topic.
Bad: "Let's talk about microservices." Good: "We cut deployment time 4x by killing our shared staging environment — here's what broke and what we learned."
Recommendation▾
Add a third example covering a failure case or bad-vs-good output comparison to reinforce quality bar
Workflow: Conference/Meetup Talk
Progress:
- Define the one takeaway (single sentence the audience repeats later)
- Pick a format: story-driven / problem-solution / before-after-bridge
- Build the outline (hook → context → tension → resolution → takeaway → CTA)
- Write the opening 30 seconds verbatim (hook must land without slides)
- Draft slide skeleton (1 idea per slide, minimal text)
- Add a controversial or surprising claim to drive discussion
- Rehearse out loud 3x, time it, cut 15% of content
- Prepare 2-3 anticipated Q&A answers
Structure template:
- Hook (30s) — surprising stat, bold claim, or short story that creates tension
- Context (1-2 min) — why this matters to this audience specifically
- Core content (60-70% of time) — 2-4 concrete lessons, each with a real example, number, or artifact (code, graph, screenshot)
- Failure/vulnerability moment — admit what went wrong; this builds more trust than success stories
- Takeaway — restate the one sentence from step 1
- CTA — what should the audience do Monday morning (not "follow me on Twitter")
Delivery notes:
- Open without reading the slide title out loud — start talking before the first slide fully registers
- Pause after key points; silence signals importance
- Convert every abstraction into a number, screenshot, or anecdote
- For internal meetings: same structure, compress to 3 steps (problem, data, recommendation), skip the hook, lead with the ask
Workflow: Expert Article
Progress:
- Choose angle: contrarian take / deep dive / case study / how-we-did-it
- Define target publication/blog and its audience expectations
- Write a headline that states the specific value, not the topic
- Draft opening paragraph with the core claim (no throat-clearing)
- Structure body with scannable subheads, each answering one question
- Insert concrete evidence: numbers, code, screenshots, before/after
- Write a conclusion with one actionable takeaway, not a summary
- Edit pass: cut 20%, remove hedging words ("maybe", "I think", "sort of")
- Add author bio positioning expertise (1-2 sentences, outcome-focused)
Headline patterns:
- "Why we stopped doing X" / "What X taught us about Y"
- "[Number] mistakes we made with X"
- "X vs Y: what nobody tells you"
Paragraph-opening rule: no article should open with "In today's world" or "Recently, X has become popular." Open with the claim or the scene.
Examples17 / 20
Example 1: Input: Senior backend engineer wants to speak at a local meetup about migrating a monolith to microservices. Output:
- One takeaway: "Migrate by business capability, not by technical layer — it's the only approach that survived our 2 failed attempts."
- Hook: "We tried to split our monolith three times. Twice we failed. Here's what was different the third time."
- Structure: hook → the two failures (concrete, with specific symptoms) → what changed → the actual migration pattern used → metrics (deploy frequency, incident count before/after) → takeaway → CTA: "audit one service boundary this week using the capability-mapping exercise I'll share."
Example 2: Input: Product manager wants to write an article establishing authority on user research. Output:
- Angle: contrarian take
- Headline: "Why We Stopped Doing User Interviews (And What We Do Instead)"
- Opening: "Last year we ran 40 user interviews and shipped the wrong feature anyway. The problem wasn't the interviews — it was that we asked questions instead of watching behavior."
- Body subheads: "The interview trap", "What we replaced it with", "The one metric that changed our roadmap", "How to try this in your next sprint"
- Takeaway: specific exercise reader can run this week.
Recommendation▾
Include a template for content strategy/cadence planning mentioned in Quick Start description but not covered in workflows
Best Practices
- Specificity beats polish: one real number beats five adjectives
- Reuse content across formats — a talk becomes 2-3 articles, an article becomes a talk outline
- Track which claims generate the most questions/comments and double down on that angle next time
- Build a recognizable point of view over time (a consistent stance, not just topics) — that's what personal brand actually is
- Publish on a cadence (e.g., monthly), consistency compounds more than virality
Common Pitfalls
- Starting with the topic instead of the takeaway — leads to generic, forgettable content
- Covering too much ground in one talk/article — one sharp idea beats five shallow ones
- Hiding failures or uncertainty — vulnerability builds more authority than a highlight reel
- Opening with agenda slides or generic context — kills momentum in the first 30 seconds
- Writing for approval instead of utility — ask "what can the reader do with this tomorrow"
- Overusing hedging language in articles — it undermines the expert positioning the piece is meant to build