11.02 · RESEARCH · THE NORTH STAR · JUN 2026
The Operating System mandate. Not just visual design.
From the operating-system meeting. The work is to create the operating system for how Diray Media thinks, communicates, builds, and ships. Everything reinforces one idea: four decades of media expertise amplified by modern AI technology. The technology is not the product. The technology amplifies the expertise.
POSITIONING · THE REFRAME
Where Diray is going.
Three positionings in three eras. The future is not a tagline: it is the operating model.
CORE STORY · ONE FLOW, MANY FORMATS
Every artifact tells the same story in the same order.
Website, pitch decks, sales presentations, emails, dashboards, client reports, marketing, case studies. One spine. Seven steps.
THE NINE PILLARS
The structure under everything.
Reorganize every output around these nine pillars. Pillars 05 and 07 (Impact Engine and Impact Score) are the hero IP. The rest support them.
Why TV.
Convince people TV still matters. Lives on the website, sales decks, explainers, social.
Modern TV.
TV is not cable. TV includes streaming, CTV, retail media, cross-screen. Needs a beautiful ecosystem visualization.
Market complexity.
One audience → hundreds of channels → thousands of placements → millions of decisions. Then: we simplify all of it.
Performance media.
Differentiate from agencies. Business outcomes (sales, revenue, orders, market share, velocity), not vanity metrics.
Impact Engine.
This becomes the product. Needs its own identity: logo, language, motion, rules, personality, components. Think Apple Intelligence, Adobe Firefly. Not a graphic, a product.
AI + Human expertise.
Five steps: Signals → AI Analysis → Human Judgment → Optimization → Business Growth. The current diagram is too busy. Simplify.
Impact Score.
Should become iconic. Every dashboard, every report, every client email, every presentation reinforces it. Today's Score, Last Week, Projected Growth, Recommendations. Clients start asking: "what's our Impact Score?"
Impact Solutions.
Shelf, Launch, Market, Demand, Efficiency, Surge become real products. Each deserves a one-pager: Problem · Solution · Result · Proof · CTA.
Proof.
Case studies are simple: Problem → Approach → Results. One page. Build dozens.
PROGRESSIVE STORYTELLING · THE DESIGN PRINCIPLE
Every slide answers one question.
The operating-system meeting identified the biggest design opportunity: every diagram tries to explain everything simultaneously. Replace the huge map with the same idea told in seven progressive moves.
INTAKE FRAMEWORK
What every engagement starts with.
A standing intake the team runs in week one of any new client engagement. Same structure every time.
Business
- Who are they?
- Industry?
- Size?
- Goals?
Objectives
- Revenue?
- Awareness?
- Retail?
- Launch?
- Demand?
KPIs
- ROAS
- Sales
- Orders
- Market Share
- Velocity
- CAC
Data
- Available?
- Clean?
- Connected?
- Missing?
Channels
- Linear
- CTV
- Streaming
- Retail
- Digital
Creative
- Assets?
- Video?
- Landing pages?
- Offers?
Technology
- CRM
- Retail
- Analytics
- Measurement
Success
- What does success look like at 30 days?
- At 90?
- At a year?
DELIVERABLES · THE STACK
The full output catalog.
What "designing the operating system" actually ships. Five categories, each owns part of the company's voice.
Foundation
- Brand system
- Story system
- Design system
- Component library
- Motion system
- Diagram system
Sales
- Master deck
- Capabilities deck
- Industry decks
- Case study templates
- Proposal templates
Marketing
- Website
- Landing pages
- One-pagers
- Thought leadership
- Impact product pages
Product
- Impact Dashboard
- Impact Score
- Client Portal
- Operator Views
- Executive Views
AI
- Claude Skills
- Prompt library
- MCP connections
- Slide generation
- Artifact generation
- Brand voice
EXECUTION ROADMAP · FOUR PHASES
Understand. Build. Systemize. Ship.
The order matters. Understand before you build, build before you systemize, systemize before you ship at scale.
Understand.
- Interview stakeholders
- Audit artifacts
- Map current systems
- Document story
Build.
- Story framework
- Messaging hierarchy
- Visual direction
- Design language
Systemize.
- Component library
- Slide system
- Diagram system
- Case studies
- Templates
Ship.
- Website MVP
- Sales deck
- Impact Engine visuals
- One-pagers
- Dashboard refinements
THE LONG ARC · TWO PLATFORMS
What the operating system ladders into.
The library, the decks, the skills are not the destination. They build toward two productized platforms that make the Diray operating model legible to operators and clients.
Media Analysis.
The operator-facing surface where Diray's team scores media in flight, sees what is working and what is not, and exposes the common-sense patterns to look for. The Media Analysis Tool and the internal company dashboard converge here.
Impact Engine.
The client-facing surface where the Impact Score lives. Every dashboard, every report, every email reinforces it. Replaces TapClicks with a Diray-owned, brand-true client view. Outcomes first, vanity metrics never.
THE ROLE · ONE SENTENCE
What Drew is actually being hired to do.
Design the operating system for how Diray communicates, sells, visualizes, and scales its expertise across every client touchpoint.
From the operating-system meeting
Not isolated artifacts. A reusable system where every deck, dashboard, one-pager, email, case study, website page, and AI-generated presentation shares the same language, structure, and visual grammar. If the system is well-built, the team generates polished, consistent client-facing material using Claude while preserving quality and dramatically reducing production time.
MCP Client Services amplifier.
The first concrete bridge from this mandate to the Media Analysis + Impact Engine platforms. A one-prompt case study builder, portfolio precision tactics, and proof-point assembler the client-services team can turn on.
Open 12.03 · MCP Client Services amplifier →