diff --git a/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md b/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md index ee1cb10f6..2a0ada195 100644 --- a/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md +++ b/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md @@ -108,6 +108,8 @@ Try to "polish the prototype into the MVP later" and you spend much longer on it Three screens is the constraint - not five, not ten - because each extra screen multiplies the build effort without sharpening the validation signal. +![Wireframe of a passing 3-screen prototype: Screen 1 entry point with a fake file list and a Match transactions button, Screen 2 core action showing a Stripe-vs-QuickBooks match table where testers stall, and Screen 3 result with a summary card and Download report - the screen a passing tester reaches without coaching](wireframe-strip.svg) + > **The two caps that replace "spend a weekend on it".** (1) **Stop at 3 screens.** The fourth screen is the prototype turning into the MVP - exactly the failure mode this chapter prevents. (2) **Aim for a navigable 3-screen prototype within your first ~10 Lovable exchanges.** If after 10 messages the screens still aren't navigable, the hypothesis or the prompt is too vague - sharpen the prompt (or go back to Ch 1.1) before continuing. Do NOT keep adding messages hoping to brute-force coherence. ### Screen 1 - The entry point diff --git a/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/wireframe-strip.svg b/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/wireframe-strip.svg new file mode 100644 index 000000000..fda7a0ab2 --- /dev/null +++ b/content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/wireframe-strip.svg @@ -0,0 +1,78 @@ + + A passing 3-screen prototype: Screen 1 entry point (fake file list + a Match transactions button) leads to Screen 2 core action (a Stripe-vs-QuickBooks match table where testers stall) leads to Screen 3 result (a summary card and Download report), which is where a passing tester lands without coaching. + + + + + A passing 3-screen prototype, wireframed + + + + + + Screen 1 · Entry point + + 3 CSV files listed + (hard-coded fake data) + + Match transactions + + First click - can they start? + + + + + + + + + + + + Screen 2 · Core action + + Stripe vs QuickBooks + 12 matched · 3 flagged + + Approve all matches + + Where testers stall + + + + + + + + + + + + Screen 3 · Result + + Summary card + 12 matched, 3 flagged + + Download report + + Can they name what it did? + + + + PASS = reaches here uncoached + diff --git a/content/course/tech-for-non-technical-founders-2026/faq/index.md b/content/course/tech-for-non-technical-founders-2026/faq/index.md index 6d227a3c3..55dfe0770 100644 --- a/content/course/tech-for-non-technical-founders-2026/faq/index.md +++ b/content/course/tech-for-non-technical-founders-2026/faq/index.md @@ -29,6 +29,8 @@ related_posts: false If you're stuck, start here. These are the questions founders ask most often - read the 2-3 that match your situation and get back to the build. If your question isn't here, try the course's [Quickstart path](/course/tech-for-non-technical-founders-2026/quickstart/) or the [How This Course Works](/course/tech-for-non-technical-founders-2026/how-this-course-works/) overview. +![Module map for this FAQ: a General group followed by Module 1 Hypothesis and smoke test, Module 2 Validate the problem, Module 3 Design from evidence, Module 4 Build it yourself, and Module 5 First paying customer - questions below are grouped in this order.](module-strip.svg) + --- ## Module 1 - Hypothesis & Smoke Test diff --git a/content/course/tech-for-non-technical-founders-2026/faq/module-strip.svg b/content/course/tech-for-non-technical-founders-2026/faq/module-strip.svg new file mode 100644 index 000000000..a7c3566ad --- /dev/null +++ b/content/course/tech-for-non-technical-founders-2026/faq/module-strip.svg @@ -0,0 +1,73 @@ + + FAQ map: questions are grouped as General, then Module 1 Hypothesis and smoke test, Module 2 Validate the problem, Module 3 Design from evidence, Module 4 Build it yourself, and Module 5 First paying customer - in that order. + + + + + + + + + + + General + pace & order + + + + + + M1 + Hypothesis + & smoke test + + + + + + M2 + Validate + the problem + + + + + + M3 + Design from + evidence + + + + + + M4 + Build it + yourself + + + + + + M5 + First paying + customer + + + + + + + + + + Find your module below - questions are grouped in this order. + diff --git a/content/course/tech-for-non-technical-founders-2026/hiring-interview-script/index.md b/content/course/tech-for-non-technical-founders-2026/hiring-interview-script/index.md index 817bd8ebf..a083635dc 100644 --- a/content/course/tech-for-non-technical-founders-2026/hiring-interview-script/index.md +++ b/content/course/tech-for-non-technical-founders-2026/hiring-interview-script/index.md @@ -48,15 +48,9 @@ related_posts: false ## The 7 questions at a glance -| # | Question (compressed) | What it tests | -|---|---|---| -| 1 | Workflow: Jira ticket to merged code, with AI in the loop | Tools named by version, real PR from last week | -| 2 | Cost: $/dev/month on AI tokens, who pays it | Specific dollar range, pulled before the call | -| 3 | Verification: what the senior reviewer checks on AI PRs | Opens a real PR on screen, names line-level checks | -| 4 | Slopsquatting: how do you stop a hallucinated package | Named defense, uses the word, cites the source | -| 5 | Accountability: last AI-generated-code incident you owned | Date in last 6 months, root cause, workflow change after | -| 6 | Refactor: last one you led, what stayed/changed/broke | Named system, kept-changed-broke-safety-net structure | -| 7 | Disagreement: PR review where you said no to the AI | Real PR on screen, specific technical reason, one of many | +Keep this card open during the call or print it: what to listen for (Pass) sits beside what to walk away from (Fail), question by question. The full criteria for each are in the sections below. + +![The 7 hiring questions on one card - the pass signal beside the fail signal for each, with a checkbox to score in real time](scorecard-at-a-glance.svg) ## Why this exists diff --git a/content/course/tech-for-non-technical-founders-2026/hiring-interview-script/scorecard-at-a-glance.svg b/content/course/tech-for-non-technical-founders-2026/hiring-interview-script/scorecard-at-a-glance.svg new file mode 100644 index 000000000..d433c84c3 --- /dev/null +++ b/content/course/tech-for-non-technical-founders-2026/hiring-interview-script/scorecard-at-a-glance.svg @@ -0,0 +1,80 @@ + + The 7 hiring questions on one card: pass signal versus fail signal for each + + + + + Run the interview from this card + Tick the box when the answer lands on the Pass side. Full criteria for each question are below. + + + + + + + Question + PASS sounds like + FAIL sounds like + + + + + Q1 + Workflow: ticket to code + Tools by version + real PR + “Cursor does boilerplate,” no PR + + + + Q2 + Cost: $/dev/month + $80-300, pulled the receipt + “My company pays,” no tracking + + + + Q3 + Verify: reviewer checks + Opens real PR, names checks + “I trust the model / CI” + + + + Q4 + Slopsquatting defense + Named defense + says the word + “Name looks right,” never hit it + + + + Q5 + Accountability: owned it + Dated incident + root cause + “Never had one,” blamed Cursor + + + + Q6 + Refactor you led + Named system: kept/changed/broke + “Refactor as I go / rewrote it” + + + + Q7 + Disagreement with the AI + Real PR on screen, specific reason + “Usually agree,” then silence + + + Refuses to share screen on Q3 or Q7 = automatic Fail on both. The interview is over. +