Humans first
Technology should support human judgment, not hide it or replace it.
Working systemVersion 0.3
AlwaysReady4Moore.com
Field Guide
The visual rules behind the portfolio: the phoenix mark, cyan signal, editorial illustrations, and notebook interface.
I build systems that help people find the right answer.
I organize scattered information, repeated work, and unclear processes into systems people can use.
The markClarity
01 / Philosophy
Make the work easier to understand
Every design decision should make the work easier to understand.
The interface should show systems thinking instead of relying on a claim.
Clarity over complexity
A useful system helps people understand what to do, where to look, and why it matters.
Observe before building
Start by observing how the work happens, including the awkward workarounds.
Build the smallest useful system
Start with a useful version. Test it in use, then expand when the evidence supports it.
Refine through feedback
Launch is the start of maintenance. Improve the system through observation and review.
Personality can support credibility
Professional work can feel warm, memorable, and human without becoming unserious.
02 / The mark
Phoenix
A mark for rebuilding fragmented information, processes, and technology into clearer systems.
Clarity is the approved mark. This section tests how it scales across the site.
Approved direction / Clarity
The mark
The phoenix represents rebuilding. The cyan spark marks a useful connection, progress, or verification.
Scale test
Single sourceLarge use
Field Guide, hero panels, documents, and larger brand moments.
Standard interface use
Header, footer, section seals, and navigation accents.
Small interface use
Cards, badges, compact labels, and small interface placements.
Very small use
Favicon testing, metadata, and very small placements.
03 / The signal
Cyan spark
A signal for a useful connection, verified result, or correct path.
Use cyan only when it communicates a state, path, or result.
The signal can communicate
ClarityDiscoveryProgressConnectionVerification
The signal does not mean
- Decoration without meaning
- Technology merely for technology’s sake
- Random sparkle or visual filler
Headline anchor
Make the useful path easier to follow
In major headings, cyan marks the phrase that carries the main point. Use one anchor and choose it for meaning, not position.
04 / Color
Use signal against structure
Dark surfaces provide structure. Paper separates editorial content. Cyan marks the useful path.
Ink
#050A0C
Primary shapes, structure, and visual weight.
Paper
#F7F8F8
Editorial surfaces and diagrams.
Night
#071014
The dark background around the work.
Surface
#101820
Cards, modules, and working areas.
Signal
#19D8E8
The correct path, progress, or verified result.
Signal Soft
#7EF3FF
Secondary emphasis and soft signal states.
Border
#26323A
Structure that separates sections without adding noise.
Muted Text
#A7B3BA
Supporting copy, metadata, and lower-priority details.
05 / Typography
Give each typeface one job
Display type sets hierarchy, body type supports reading, and lab type labels the system.
Use handwritten type only for occasional annotations.
Display
Make the system easier to understand.
Large headlines, case-study titles, major section introductions, and strong editorial statements.
Body
Useful systems make the right information easier to find, understand, and act on.
Long-form reading, supporting copy, case-study narratives, and explanatory text.
Lab
SYSTEM STATUS / ACTIVE
Labels, system metadata, status text, navigation details, and operational annotations.
06 / Writing and voice
Lead with the point
Use plain language, active verbs, sentence-style headings, and specific evidence. Keep the warmth, but cut the setup.
The goal is useful copy that sounds like a person, not a template.
Write this way
- Lead with the point or next action.
- Use sentence-style capitalization for headings and labels.
- Choose familiar words and active verbs.
- Use contractions when they sound natural.
- Keep one term for each concept.
- Cut setup, filler, and repeated claims.
- Use lists only when they make scanning easier.
- Keep humor brief and tied to the subject.
Avoid
- Vague claims such as innovative, powerful, seamless, or game-changing
- Repeated turn-this-into-that formulas
- At the intersection of
- Not just X, but Y constructions
- Three abstract nouns where one direct sentence will do
- Overstated conclusions that the evidence cannot support
07 / Notebook language
Keep the notebook language functional
The portfolio is a working record of observations, experiments, systems, and lessons.
Notebook details should add context or humanity without making the site feel like a scrapbook.
Margin notes
Short observations that add context without interrupting the main narrative.
Tabs
Small labels that show visitors where they are.
Sticky notes
Questions, unfinished thoughts, versions, and active experiments.
Cyan arrows
Directional marks that show the path through information or work.
Paperclips
A shorthand for relationships, evidence, and connected ideas.
Coffee rings
Use sparingly to show that the work is active and lived-in.
08 / Editorial system
Show people working inside systems
Recurring editorial characters that show people working inside systems.
“The Lab Crew” is an internal name. Visitors only need a consistent visual world.
researcher
The Researcher
Find the right answer.
Represents
InvestigationTroubleshootingResearchField Notes
Common behaviors
- Following a cyan trail
- Comparing information
- Inspecting labels
librarian
The Librarian
Organize information so someone else can succeed.
Represents
Knowledge systemsDocumentationSOPsInternal wikis
Common behaviors
- Sorting
- Indexing
- Shelving
builder
The Builder
Build working systems from tested ideas.
Represents
PrototypesAI workflowsAutomationExperiments
Common behaviors
- Assembling
- Testing
- Sketching
guide
The Guide
Show someone the next step.
Represents
TrainingOnboardingEnablementCommunication
Common behaviors
- Explaining
- Directing
- Welcoming
guardian
The Guardian
Protect people without creating unnecessary friction.
Represents
SecurityGovernanceTrustHuman review
Common behaviors
- Reviewing
- Checking access
- Approving requests
assistant
The Assistant
Remove repetitive work while keeping people in control.
Represents
AI assistanceAutomationSortingWorkflow support
Common behaviors
- Carrying
- Sorting
- Highlighting
09 / Motion
Use motion to clarify state
Motion should clarify state, direction, or interaction. It should never compete with the work.
button
A small lift that confirms interactivity.
card
A small lift with a stronger border or signal accent.
signal
A soft pulse for status, discovery, completion, or the correct path.
notebook
A slight slide, page shift, or corner movement when it supports the notebook metaphor.
Working principle