Interactive graph

Outcomes Over Pitch Decks

Created Jul 24, 2026, 10:27 AM · Updated Jul 24, 2026, 10:27 AM

Table of Contents

Judge vendors, frameworks, and internal champions by what they produce - not slide polish, not LinkedIn aura.

Key Concept

Judge vendors and champions by fruit over time, not slide polish or LinkedIn aura.
Level 1: Judge people and vendors by what they actually produce over time - like picking the teammate who scores, not the one with the fanciest uniform.
Level 2: Outcomes over pitch decks means fruit over time beats slide polish and LinkedIn aura.
Level 3: Champions and vendors earn trust by delivered results - decks and profiles are marketing until the work proves itself.
Level 4: Before you hire or partner, ask for three past outcomes with names attached - polish without fruit is expensive theater.
Level 5: People-Centered Design and Own the Error test the same bar - Staged Rollout beats a demo that never shipped.
Smooth talkers ship thorns sometimes.
I look at downstream stress, turnover, delivery, and whether the team got healthier or more brittle.
On Static Site Client Scope, same filter: pick WordPress or Shopify when the fruit requires it - do not sell Free Tier Hosting Stack because it is my favorite hammer.
Do not write people off on vibes alone; read outcomes over time.
Gospel source: By Their Fruits.
PKM parallel: Signal vs Noise.

The trainer's Instagram was polished - I asked two parents who finished the program about injuries and consistency.
The contractor's portfolio was gorgeous - I asked two neighbors who lived through the remodel about permit fights and cracked tile.

Relationship	Wikilink	Reason
contradicts	Life Before Achievement	when judging by results would excuse lethal methods that “worked”
contradicts	Signal vs Noise	when I cannot tell a slick pitch from real signal
extends	By Their Fruits	Discern teaching and leaders by outcome, not charisma
extends	Free Tier Hosting Stack	Judge the stack by what ships - not slide charisma
extends	Static Site Client Scope	Pick client stack by needed outcome, not by my preferred tool

Static Site Client Scope
Pick stack by what the client needs to produce, not my preferred tool
Execution
Fruit beats deck polish

Process Mapping
when the deck ships before anyone maps real work
Measure Then Iterate
when charisma replaces a metric you would actually track
Shadow the Work
when the deck wins before anyone watches real work
People-Centered Design
when slick decks beat watching one real user struggle
Notice the Good
when only results get praised and the steady process gets ignored
Duty of Care
when the opposite frame fits better
Ethical Leadership
when the opposite frame fits better
Life Before Achievement
when judging by results would excuse lethal methods that "worked"

Follow Christ, Then Lead
Judge by fruit after obedience - not pitch charisma over Christ's command

People-Centered Design
Design for real human needs first - customers, teammates, stakeholders - or the change will not stick.
Own the Error
Owning the error is naming the miss clearly so failure becomes information, not blame theater.
Staged Rollout
Ship to a small slice first so rollback stays cheap if the new state bleeds.
Static Site Client Scope
Static sites fit text and images on git push - not live databases or mystery WordPress admins.
Free Tier Hosting Stack
Hugo, GitHub, and Cloudflare Pages ship static sites for $0 - until build caps, queues, or account limits bite.
By Their Fruits
Teachers are checked by what their teaching produces, not by how polished the talk sounds.
Signal vs Noise
Save only what changes what you do or believe this month - most feeds are noise.
Life Before Achievement
Human life is non-negotiable - even when the goal is a championship or a reputation for toughness.