IrvingSpace  ·  Brand System Guidelines

The complete system
for a brand that asks
better questions.

Everything that ships under the IrvingSpace name passes through here first. What we say. How we show up. The moves that make something ours.

Version v1.1.3
Year 2026
Brand irvingspace.com
Contact john@irvingspace.com
01 — Strategy
Brand Platform

The strategic foundation that every visual and verbal decision is built on. If something looks or sounds off-brand, it's usually because it conflicts with something here.

What IrvingSpace Is (and isn't)
It is
"A place to work through ideas in public — because writing is how I figure out what I actually believe."
It is not
"Generic thought leadership. Not a portfolio of deliverables. Not a hub of frameworks to download. The writing earns credibility through the quality of thinking — not by claiming expertise."
The distinction: IrvingSpace is thought leadership — the goal is to be seen as a credible, original thinker whose writing people seek out and cite. The difference from generic thought leadership is execution: no jargon, no listicles, no borrowed frameworks dressed up as insight. Credibility is earned through the sharpness of the thinking, not through claiming authority.
Positioning
Core positioning statement
"The failure mode isn't bad execution. It's that the problem was misframed before anyone noticed it needed framing."

IrvingSpace occupies a specific gap: between the people producing frameworks and the people asking why their team keeps shipping the wrong thing confidently. It's not for people looking for quick answers. It's for practitioners who've been in enough rooms to wonder if the room itself was the problem.

ProductAISystemsProblem DefinitionMeasurement
Audience
The practitioner
Someone inside a team — product, strategy, or adjacent — who's been in enough rooms to notice when the problem framing is wrong but hasn't always had language for it.
The slow reader
Not consuming content for takeaways. Looking for something that actually makes them stop and think. Suspicious of frameworks. Interested in questions more than answers.
The person building in AI
Working at the intersection of AI and product, and noticing that AI makes it easier to ship and harder to know what you should be shipping. The gap is the thing.
Not the audience: Anyone looking for news, career advice, or motivational content. IrvingSpace doesn't serve those needs on purpose.
Three core ideas — the lenses

Not a framework. More like standing questions that shape what gets written, what gets published, and how the space works.

01
The problem space
There's a point where every team shifts from asking "what's actually happening?" to "how do we fix it?" That shift is almost always premature. And almost never noticed. Knowing where you are on the problem-to-solution spectrum changes everything.
02
Systems thinking
Every black box is a set of choices someone made for conditions that no longer apply. Systems thinking is the practice of seeing structure under behavior. Incentives create behaviors. Behaviors reinforce structures. Structures outlast the rationale that created them.
03
Tracking results
Most teams define success after the thing is built — and the definition lands on whatever the thing happens to be doing. That's not measurement. It's retroactive justification. Very few teams can finish the sentence: "we'll know this worked when…"
02 — Visual Identity
Color System

The palette is organized into three groups: surfaces (where things live), text (how type reads), and accents (reserved for specific moments).

Surfaces & backgrounds
Cream
#F7F4EE
Primary background, nav, cards
Cream 2
#F0ECE4
Section alternates, writing bg
Cream 3
#EDE8DF
Card backgrounds, panels
Border
#E3DDD5
Dividers, borders, grid gaps
Dark
#1C1A17
Featured sections, headers
Espresso
#0D0A06
Hero, footer, logo base
Text colors
Primary
#1C1A17
Headlines, body on cream
Secondary
#5A5550
Body copy, nav links
Muted
#AAA59F
Labels, dates, metadata
Ink Blue
#1B3A5C
Tags, featured items, links
Warm Brown
#6B5E3E
Eyebrows, sidebar labels
Amber
#A8906A
Links on dark backgrounds
Neon accents — hero & illustrations only
Neon Yellow
#FFE537
Hero headline, logo dot, primary CTA
Neon Forest
#00C44A
"Read writing" hover state
Neon Red
#FF3B3B
"About" hover, don't indicators
Neon Teal
#00C9B8
Systems thinking, nav hover
Neon Coral
#FF5C35
Tracking results, charts
Neon accent rule: Neon colors live primarily on dark (espresso/dark) backgrounds — the logo dot, hero moments, and interactive states. They are rarely used on cream surfaces, and only when the color has enough depth to hold contrast (Neon Forest is the clearest example). Casual or decorative use on cream dilutes their signal.
02 — Visual Identity
Typography

Two typefaces. One does the editorial heavy lifting; the other gets out of the way. The tension between them is intentional — serious ideas, clean delivery.

Editorial
Georgia
Serif · System font · Used for: headlines, card titles, pull quotes, wordmark, hero copy
UI
System Sans
Used for: body copy, nav, labels, buttons, metadata, eyebrows
Type scale
Role Example Spec
Hero headline Are you solving for Georgia · 38px
Section / card title The problem space Georgia bold · 20px
Post / article title Everyone Is Shipping. Very Few Can Finish the Sentence. Georgia · 16px
Body copy Most teams skip problem definition entirely and pay for it later. Sans · 14px · lh 1.75
Label / eyebrow Three ideas that shape how I look at most things Sans · 9px · ls 1.8 · UC
Button / CTA Read the Writing Sans bold · 11px · ls 0.8
03 — Voice
Brand Voice

Voice is the personality that shows up in every sentence — not just tone, but the actual structure of how ideas are expressed. IrvingSpace has a specific voice that should be recognizable even without the visual branding.

"I'm not here to tell you what to build. I'm here to ask better questions about why."
— — John Irving · IrvingSpace
Voice traits
Ask, don't assert
Lead with questions. The headline is often a question. Ideas create space for thinking, not conclusions to download. If a sentence sounds like a lecture, rewrite it as a provocation.
Not: "Here's why X matters." — Yes: "What would it mean if X wasn't true?"
Short over long
Card bodies are 1–2 sentences. Let the writing do the work — the UI and the setup stay short. If you need three sentences to make the point, the point isn't clear yet.
Not: a paragraph that builds to something. Yes: the thing, with the paragraph behind a click.
Warm but direct
No hedging. If it's true, say it. The warmth comes from the quality of thinking, not the softness of the phrasing. "Most teams" is more honest than "some teams might consider."
Not: "It may be worth exploring whether…" — Yes: "Most teams skip this entirely and pay for it later."
Examples
Don't
In today's fast-paced world, teams need to leverage solutions to drive outcomes and create value.
Do
"Most teams skip problem definition entirely and pay for it later."
Don't
Here are 7 actionable frameworks for measuring AI success at your organization.
Do
"Very few people can finish the sentence: "we'll know this worked when…""
Don't
Welcome to IrvingSpace, your go-to resource for product and AI insights.
Do
"It's not a personal brand play. It's a place to work through ideas in public."
Don't
As a thought leader in the AI space, I want to share my perspective on the future of product management.
Do
"The failure mode isn't bad execution. It's that the problem was misframed before anyone noticed it needed framing."
Signature structural moves
Open in another domain
Ground the abstract idea in a concrete history before naming it: the printing press, photography's effect on painters, FMEA in the military, the jury that deliberates only after all evidence is in.
e.g. Seen in: collapsing moats, failure modes, problem definition.
Draw the distinction
The core move is separating two things that get conflated, then marking the gap plainly. "Those are not the same thing." The essay lives in that gap.
e.g. Symptom vs. problem. Activity vs. outcome. Survival vs. sound design.
Land it on one line
After a paragraph builds, drop a single short line on its own. The white space carries the emphasis, not bold or punctuation.
e.g. "Sign-ups don't recover." / "It got assumed."
Also recurring: credible data woven in as proof (Ahrefs 96.55%, Edelman 73%, Nielsen 85%), and a full Sources list closing every essay. Evidence is cited, not name-dropped.
Vocabulary
Use
  • problem space / solution space
  • misframed / framing
  • feedback loop / system
  • assumption / unstated assumption
  • teams, practitioners, builders
  • working through, navigating, exploring
  • notice, see, recognize
  • precisely, specifically
  • almost always, most teams
  • the thing
  • failure mode (the specific way it breaks)
  • table stakes
  • leading / lagging indicators
  • vanity metric
  • the tell
  • name the pattern
Avoid
  • leverage, synergy, ecosystem
  • self-described guru, oracle, visionary
  • actionable, scalable, impactful
  • in today's [anything]
  • disruptive, innovative, game-changing
  • journey, transformation, pivot
  • holistic, robust, seamless
  • go-to resource, one-stop
  • best practices (without critique)
  • share my perspective on
Tone by context
Context
Tone
Example
Writing / essays
Direct, questioning, unhurried. The reader has chosen to slow down.
There's a point where every team shifts from 'what is this?' to 'how do we fix it?' That shift is almost always premature.
Homepage / UI copy
Short, declarative. Functions like a sign, not a pitch. Creates curiosity, doesn't resolve it.
Are you solving for the right problem?
About / context
Honest, specific, no performance. Explains what this is without selling it.
It's not a portfolio. It's a place to work through ideas in public.
Email / newsletter
Conversational but substantive. Like a note from someone who's been thinking hard about something.
Something I keep noticing: the cleaner the AI output, the easier it is to skip the question it was answering.
Social / short-form
One provocation. No thread of takeaways. Resist the pull to over-explain.
Most teams can't finish this sentence: 'we'll know this worked when…'
04 — Messaging
Messaging Framework

The structured hierarchy of what IrvingSpace says — from the core message down to proof points and headline patterns. Voice is how we say it; messaging is what we're always saying.

If IrvingSpace could only say one thing, it would be this:
Core message
"The failure mode isn't bad execution. It's that the problem was misframed before anyone noticed it needed framing."

Tagline: Are you solving for the right problem?

Value prop: A place to work through ideas in public — about what teams get wrong before they build anything.

Live taglines from the writing index: "The questions worth slowing down for. Notes from inside the work." Plus the standing essay description: "attempts to name something that wasn't obvious to me until the third or fourth time I ran into it."

Key messages — the three pillars
Message 01
Problem framing is the work that precedes the work
Teams who skip problem definition end up building the right solution to the wrong problem. The diagnostic period isn't delay — it's the highest-leverage part of any project.
Message 02
Every organization is a system with invisible feedback loops
Incentives create behaviors. Behaviors reinforce structures. If the same problem keeps reappearing in a new hat, it's not a people problem — it's a structure problem.
Message 03
You can't measure what you define after the fact
Most teams define success to match what they built. Real measurement is decided before building. "We'll know this worked when…" is a sentence that must be completable before the sprint starts.
Headline patterns
Examples by context
Hero
"Are you solving for the right problem?"
Essay / Post
"When Everyone Has the Same Content Operations, What's Your Actual Differentiator?"
Essay / Post
"Is AI Hiding Our Failure Modes?"
Essay / Post
"What Is a KPI and How Do You Determine Them?"
Essay / Post
"The Difference Between Understanding a Problem and Solving It"
Social
"Most teams can't finish this sentence: "we'll know this worked when…""
Newsletter
"Something I keep noticing about AI and problem definition."
05 — Rules
Usage Rules

Applied rules for every element of the system. Use these to evaluate any new piece of work — a page, a post, a social card, a template.

Color application rules
Do
  • Use cream surfaces (#F7F4EE, #F0ECE4, #EDE8DF) as the primary canvas
  • Use espresso (#0D0A06) for hero, footer, and featured dark sections
  • Reserve neon accents exclusively for dark surfaces
  • Use Ink Blue (#1B3A5C) for tags, links, and featured content markers
  • Let border (#E3DDD5) do the structural work — not heavy shadows
Don't
  • Use neon colors casually on cream — only when contrast is sufficient and the use is intentional
  • Mix more than one neon accent on the same surface
  • Use color to decorate — only to communicate (state, category, emphasis)
  • Introduce colors outside the defined palette
  • Use gradients or color fills on backgrounds
Typography rules
Do
  • Use Georgia for all headlines, pull quotes, and the wordmark
  • Use system sans for all body copy, labels, and UI elements
  • Set eyebrows in all-caps with 0.18em letter-spacing
  • Use italic Georgia for quotes, pull quotes, and editorial captions
  • Follow the type scale — don't introduce new sizes outside it
Don't
  • Mix serif and sans in the same sentence or heading
  • Use bold on Georgia body text (only bold for card titles)
  • Use all-caps on body copy or headlines
  • Set body copy smaller than 12px
  • Use decorative fonts or any typeface outside the defined pair
Visual motifs — surfaces explored so far
Do
  • Use the grid motif (faint 28–32px grid) on dark backgrounds as texture
  • Use the directional mark (compass) as illustration/icon, not decoration
  • Let SVG illustrations be diagrammatic — charts, flows, systems maps
  • Apply radial gradient masks to fade grid patterns toward edges
  • Keep illustrations monochromatic on cream, accent-colored on dark
  • Try new surfaces — photography, richer imagery, motion — deliberately, and ship them if they hold to the voice
Don't
  • Use the grid at full opacity — it should always be subtle (3–6%)
  • Fill illustrations with multiple colors — pick one accent per piece
  • Use decorative flourishes unconnected to the ideas in the content
  • Ship stock imagery or off-the-shelf icon libraries without asking why this over drawing our own
  • Treat what we haven't tried yet (photography, richer imagery, motion) as ruled out — unexplored is not the same as forbidden
Content & writing rules
Do
  • Start with the idea, not the setup for the idea
  • Use "I" only when it's essential — avoid first-person performance
  • Let a question be the headline when the piece is exploratory
  • Be specific — "most teams" is better than "some people"
  • Write the piece before the card copy — the card should compress, not tease
  • Cite real sources: every essay closes with a full citations list, not name-drops
Don't
  • Publish numbered list posts ("7 ways to…")
  • Use "I'm excited to share…" or announcement framing
  • Write to perform expertise — write to actually work something out
  • End with a call to action that undercuts the thinking
  • Post content that could have been an email newsletter blast
05 — Rules
Brand Checklist

Use before publishing any piece of content, page, or campaign. The checklist mirrors the usage rules, condensed to yes/no questions.

Pre-publish checklist
✓
Strategy
Does this create space for thinking, or does it try to close it? (Publishing conclusions is not on-brand.)
✓
Strategy
Does this piece demonstrate a specific, earned perspective — not just an opinion? Good thought leadership requires a distinct point of view backed by real thinking.
✓
Voice
Does the headline ask, provoke, or observe — not instruct or promise?
✓
Voice
Is any avoided vocabulary present? (leverage, actionable, journey, game-changing…)
✓
Voice
Is the UI/card copy under 2 sentences?
✓
Color
Are all colors from the defined palette? No new colors introduced?
✓
Color
Are neon accents used only on dark (espresso/dark) backgrounds?
✓
Type
Georgia for headlines/quotes, system sans for body/UI — never mixed in the same element?
✓
Type
Eyebrows in all-caps with letter-spacing? Body copy at 14px minimum?
✓
Logo
If the logo is used: is it on cream or espresso only, with correct clear space?
✓
Motifs
If imagery is used, has it earned the surface — does it carry meaning or just fill space?
✓
Messaging
Does the content connect — however loosely — to one of the three core ideas?