What every specialist actually does
A multidisciplinary thinking studio that specializes in digital projects. 22 specialists, 22 ways of seeing the same challenge.
All examples are drawn from the same challenge: You're leading a 6-month project to design and launch a new digital presence for a boutique creative agency: brand refresh, new website, and client-facing project portal. Fixed launch date. Team of 5. Budget: $90K. See how each specialist approaches it differently.
Vision & Strategy
Holds the long view. The Founder role keeps every decision anchored to a founding thesis, the core insight about why this project deserves to exist and who it ultimately serves. Thinks in years, not sprints. Asks "why are we building this?" when the team gets lost in features.
Key Questions
- What problem are we really solving: the surface problem or the deeper one?
- Who are the key stakeholders and what does success look like for each of them?
- What does a successful launch look like in 6 months?
- What do we refuse to build, and why?
- What makes this project different from every agency website launched this year?
Delivers
Example Output
"The real insight here isn't a website. It's a reputation system."
Most agency sites are portfolios. Static. Past tense. This one should feel like the agency is working live: active case studies, a visible process, a portal that clients actually use.
Project position:
- We're not building a website. We're building the agency's primary business development tool.
- Tag line territory: "An agency site that closes deals, not just impresses people."
- What we refuse to build: a blog, a news section, a team bio page that no one reads. If it doesn't serve a prospect or a client, it's out of scope.
Maps project strategy to business outcomes across phases. The Product Strategist decides what to prioritize first, what creates lock-in, and which metric matters most right now. Thinks in sequences: what must be true before the next thing can work.
Key Questions
- What's the must-win deliverable that unlocks everything else?
- What decision made in phase 1 makes phase 2 easier or harder?
- Which milestone matters most at this stage?
- What must be true before we start the next phase?
- What's the fastest path to stakeholder sign-off?
Delivers
Example Output
Phase 1 foundation (weeks 1–4):
Brand system first. Everything else depends on it: website design, portal UI, marketing copy. If brand direction isn't locked by week 4, the entire project slips.
Phase 2 core build (weeks 5–14):
Website and portal built in parallel. Weekly client check-ins starting week 6. No surprises at final review.
Strategic constraint:
Don't start copy until the site structure is approved. Scope creep starts in the copy phase. Lock structure first.
Evaluates business model viability, unit economics, and competitive moat. The Business Consultant connects project decisions to revenue, cost, and defensibility. It flags when a great project idea is a bad business.
Key Questions
- How is the $90K split across brand, design, and build, and is that the right ratio?
- Who is the economic decision-maker and who is the day-to-day stakeholder?
- What's the cost of a 4-week delay in launch?
- Where is the project most exposed to scope creep?
- What does ROI look like 12 months after launch?
Delivers
Example Output
Recommended budget split:
Brand: $18K (20%), Website design + build: $45K (50%), Portal: $18K (20%), QA + launch buffer: $9K (10%).
Risk flag:
- Stakeholder count: Two decision-makers with different priorities is a scope risk. Agree on a single approval owner before kickoff.
- Portal scope: Client portals routinely double in scope. Define "done" for the portal in writing at week 1. Not "nice to have" vs "must have." Done vs not done.
- Buyer framing: The founder cares about new business. Frame every decision around that. "Will this help close a deal?" is the filter.
Keeps the ship pointed at the right destination. The PM translates strategy into prioritized, executable work, breaking ambitions into sprints, surfacing blockers, and maintaining focus when everything feels equally urgent.
Key Questions
- What's the one thing we absolutely must deliver this sprint?
- What dependency is blocking us?
- What does success look like for this phase?
- What is NOT in scope and why?
- Who owns this and by when?
Delivers
Example Output
Phase gate: end of week 6
Brand approved, site map approved, portal scope locked in writing. Nothing moves to design until all three are signed off.
- Week 1–2: Discovery and brief. Stakeholder interviews. Competitive review. Brand audit.
- Week 3–4: Brand concepts. Two directions. One decision.
- Week 5–6: Site wireframes and portal scope document. Client approval required to proceed.
- Each phase needs a single approval owner. Define that person at kickoff. Not "the team." One name.
Research & Discovery
Synthesizes market data, competitive landscape, and trend signals into strategic intelligence. The Research Analyst finds what's true about the world outside the project: market size, competitor weaknesses, user sentiment, and emerging shifts.
Key Questions
- Who are the agencies winning in this space and what makes their digital presence work?
- What do the best agency sites do that most agency sites don't?
- What do clients say they actually look for when vetting an agency?
- What trend is changing how clients choose agencies right now?
- What does no agency site currently communicate clearly?
Delivers
Example Output
Top patterns from 20 agency site reviews:
- Best sites: case studies with outcomes, not just process. "We increased revenue by 34%" beats "we redesigned their identity."
- Common failure: "Our work speaks for itself." It doesn't. Clients need context, not confidence.
- Emerging pattern: agencies with visible process docs and client-facing portals win more trust during the proposal stage.
The gap: No competitor in this tier shows the work AND explains the thinking AND gives clients a transparent working environment. That's the opportunity.
Uncovers what users actually need versus what they say they need. The UX Researcher watches behavior, not just feedback. It finds the workarounds, frustrations, and surprising use cases that reveal the real project scope to define.
Key Questions
- Where do users get stuck and what do they do about it?
- What workarounds have they invented?
- What's the trigger that makes someone switch tools?
- What does success look like from the user's perspective?
- What do users say they want vs. what they actually do?
Delivers
Example Output
Unexpected finding:
6 of 8 clients interviewed said they check an agency's site AFTER a referral, not before. The site doesn't start relationships. It confirms them.
Implication:
The site isn't a discovery tool. It's a trust-confirmation tool. That changes everything: less "sell the agency," more "make the decision easy." Social proof, case study depth, and clear process matter more than hero animations and awards.
Job-to-be-done: "When I'm referred to an agency, I want to confirm they're legit and know what I'm getting into before I email them."
Design
Creates clear, efficient, accessible experiences. The UX Designer reduces friction, eliminates unnecessary steps, and ensures users can accomplish their goals without confusion, on any device.
Key Questions
- What's the minimum number of steps to the user's goal?
- Where can we eliminate a decision point?
- What does the user expect to happen here?
- Is this accessible on mobile?
- Where does the user's mental model break?
Delivers
Example Output
Current proposed structure: 9 pages
- Home, About, Team, Services, Work, Case Studies, Blog, Contact, Portal Login
Proposed: 5 pages + portal
- Home: What you do, who it's for, proof it works (3 case studies)
- Work: Case studies with outcomes. No grid of pretty pictures.
- Process: What working with you looks like. Answers the "what do I get?" question.
- About: One page. Team photo is optional. Clients hire the work, not the headshots.
- Contact: One form. No "Book a call" widget that asks for budget upfront.
About, Team, Blog, Services: merged or removed. If a prospect needs to click 4 times to understand what you do, you've already lost them.
Crafts the visual language of the project. The UI Designer makes every screen feel intentional: hierarchy, weight, spacing, and color working together so the eye lands in the right place without effort.
Key Questions
- Does hierarchy guide the eye to what matters most?
- Is the design system consistent across all screens?
- What's competing for visual attention that shouldn't be?
- Does this feel premium or generic?
- Are we using white space as a design tool?
Delivers
Example Output
Problem identified:
The homepage has 6 competing visual weights. The hero, nav, case study grid, testimonials, and CTA all fight for attention at the same level.
Proposed 3-level hierarchy:
- Level 1: Primary action: One CTA above the fold. "See our work" gets the accent color. Nothing else does.
- Level 2: Supporting content: Case study cards, testimonials. Surface-colored, border only.
- Level 3: Utility: Nav links, footer, metadata. Subdued. Never competing with primary.
Three levels, no exceptions. A prospect should know where to look in under 2 seconds.
Finds moments where the project creates emotional connection. The Experience Engineer asks what users will remember, share, and tell colleagues about. Then it designs those moments deliberately.
Key Questions
- What will users screenshot?
- What moment will they describe to a colleague?
- What's the first impression when they log in?
- What does the empty state communicate?
- How do we celebrate a team win?
Delivers
Example Output
Opportunity: project delivery moment
Currently: the client gets a Dropbox link and a Loom video. Professional but forgettable.
Proposed experience:
When a project milestone is delivered through the portal, the client sees a single, quiet card:
"✦ Brand System delivered · Ready for your review"
No modal. No email with 11 attachments. Just the deliverable, beautifully presented, with a single "Leave feedback" button.
The moment feels considered, not transactional. Clients remember how delivery feels, not just what was delivered.
Ensures brand consistency and strategic visual direction. The Creative Director maintains a strong point of view about what the project looks, sounds, and feels like. It pushes back when execution drifts from that vision.
Key Questions
- If the project had a personality, what would it be?
- What makes this look different from every competitor?
- Is every screen recognizably the same project?
- What reference points set the aesthetic north star?
- Does the visual language support or undermine the brand?
Delivers
Example Output
Current aesthetic diagnosis:
The agency currently reads as "generic dark portfolio," same as 80% of boutique creative agencies. Black backgrounds, white type, a Neue Haas Grotesk clone, and a grid of case study thumbnails.
Direction: "Considered Practice"
- Warm off-white backgrounds: the work lives in a gallery, not a cinema
- Serif headlines with weight contrast: editorial, not tech-startup
- White space that communicates confidence, not emptiness
- Photography: process shots, not renders. Real work, not stock.
Reference: Pentagram's editorial clarity + Wolff Olins' conceptual confidence + a smaller studio's personal warmth.
Builds the identity and positioning that creates lasting preference. The Brand Strategist defines what the brand stands for, how it speaks, and what users feel when they encounter it. Then it makes sure every touchpoint reflects that.
Key Questions
- What do users say about us to their colleagues?
- What emotion does the brand evoke? Is that intentional?
- What does the name communicate before anyone reads the tagline?
- What's our positioning vs. the category leader?
- What values are we willing to take a stand on?
Delivers
Example Output
Positioning problem:
- Current: "We're a full-service creative studio." (Every agency says this.)
- Avoid: "Strategic + creative." (Also everyone.)
- Direction: A specific, ownable point of view about what great creative work actually requires.
Positioning statement:
"For founders who know what they want but can't get their team to see it yet."
Contrast position: other agencies make things beautiful. This agency makes the vision legible. Clients don't come for aesthetics. They come for alignment.
Craft
Words are a project surface. Every headline, CTA, error message, tooltip, and empty state is designed with the same intentionality as the UI. The Copy Strategist shapes what the project says, how it says it, and whether users trust it.
Key Questions
- Does this CTA say what users get, not what they do?
- Is the error message helpful or just true?
- Does the voice stay consistent across all screens?
- What is the user feeling right now, and does the copy match that?
- Is the headline answering the user's first question?
Delivers
Example Output
Hero headline rewrites:
Before: "We create brand experiences that move people."
After: "Brand and digital work for founders who need their vision to land."
CTA rewrites:
Before: "Let's talk"
After: "See how we work"
Case study intro rewrite:
Before: "A brand refresh for a fast-growing SaaS company."
After: "They had a product people loved. The brand didn't match it. We fixed that in 8 weeks."
Voice principle: Outcomes over process. Specific over general. Always answer: what changed?
Creates visual motion that communicates, persuades, and builds trust. Every animation has a job: revealing meaning, guiding attention, or building emotional resonance. Benchmarks against Apple, Stripe, Linear, Framer, Vercel.
Key Questions
- What's this animation's job: awareness, trust, or conversion?
- Does this motion communicate something words can't?
- What happens on mobile: same or simplified?
- Does this pass the reduced-motion test?
- Is this under 200ms?
Delivers
Example Output
- Hero Objective: Communicate creative precision, not just capability. Emotional goal: "These people are serious about their work."
- Visual Concept: A live design process: a grid of case study thumbnails resolving into focus, one by one. Like a contact sheet coming to life.
- Motion Concept: Deliberate pace. Images don't rush in. They settle. Ease-out cubic. Each element lands with purpose.
- Interaction Model: Auto-plays on load. No interaction required. Pauses if user scrolls.
- Tech Stack: GSAP timeline + CSS grid. No Three.js. This is a portfolio, not a product demo. Performance over spectacle.
- Mobile Strategy: Static hero image. Best case study on top. No JS animation on mobile.
- Conversion: Animation ends on a completed case study card. CTA fades in: "See all our work." Sequence creates the "I want to know more" moment.
Makes interactions feel polished, fast, and intentional at the code level. The Front-End Experience Engineer bridges design and engineering, ensuring the project feels as good in the browser as it looks in Figma.
Key Questions
- Does this hover state give meaningful feedback?
- Is the loading state communicating progress or just spinning?
- What's the perceived performance: even before the data loads?
- Are transitions GPU-composited (transform/opacity only)?
- Does this feel like a $200/mo tool or a free tool?
Delivers
Example Output
Issue found:
Case study images load without a placeholder. On slow connections, content jumps 400px when images load. The layout shift makes the page feel unfinished.
Fix (4 lines of CSS):
Add aspect-ratio: 16/9 to all case study image containers. The space is reserved before the image loads. No jump. No shift.
Add a skeleton shimmer: a subtle linear-gradient animation on the background while loading. Signals activity without a spinner.
The page now feels stable on first load. Perceived performance is real performance. Users don't measure milliseconds. They measure how stable things feel.
Technology
Designs the system that makes everything else possible. The Architect thinks in trade-offs, failure modes, and 10x scale, making sure the technical foundation doesn't become the project's ceiling.
Key Questions
- What's the data model and does it support all planned features?
- How does this scale to 10,000 teams?
- What's the blast radius if this service fails?
- What are we building that we should be buying?
- Where are the performance bottlenecks at scale?
Delivers
Example Output
Portal architecture decision:
Don't build it. Integrate it. Tools like Notion, Basecamp, or a white-labeled client portal SaaS will take 6 weeks to integrate. Building from scratch takes 6 months. Your differentiation is the design, not the infrastructure.
The real architecture problem:
File delivery and version control for client deliverables. Don't use email attachments or Dropbox folders. Use a CDN-backed asset system with version tracking. Every deliverable should have a URL, a version number, and a timestamp.
Scope risk:
Real-time collaboration features will double your build time. Define "portal" as: view deliverables, leave comments, approve milestones. That's it. Real-time editing is a v2 conversation.
Instruments the project to learn continuously. The Analytics Lead defines what success looks like before shipping, setting up the measurement infrastructure that tells you what's working, what's not, and why.
Key Questions
- What's our North Star Metric?
- What does "activated" mean for this project, specifically?
- What events do we need to track before launch, not after?
- How do we measure quality, not just quantity?
- What does a healthy cohort look like at 30/60/90 days?
Delivers
Example Output
North Star Metric:
"Qualified inbound leads per month, 90 days post-launch."
Not pageviews. Not bounce rate. Those are vanity. A creative agency's website has one job: start conversations with the right clients.
Leading indicators to track from day one:
- Week 1: Time on case study pages (target: avg 2min 30s)
- Week 2: Contact form completion rate (target: 4% of case study visitors)
- Month 1: Portal login frequency from active clients (target: 2x/week per project)
Define these before launch. If you wait until after, you're measuring activity, not outcomes.
Designs intelligent features that feel helpful, not intrusive. The AI Systems Designer asks where AI genuinely reduces work, not where it adds "AI" for its own sake, and designs for the reality that AI outputs are probabilistic, not deterministic.
Key Questions
- Where is AI reducing real user work, not just adding features?
- What's the user experience when AI is wrong?
- Do users have a clear override path at every AI decision?
- How do we instrument AI quality: accept, edit, reject rates?
- What does graceful degradation look like when AI is slow?
Delivers
Example Output
Opportunity:
Client fills out a project intake form. AI drafts a project brief with scope, timeline, and open questions, based on intake responses and comparable past projects.
AI UX principles for this feature:
- Present as draft, not final. "Here's a starting point," not "Your brief is ready."
- Inline editing. Every AI-generated line is editable. Clients need to feel in control of their own brief.
- Source transparency. Hover a generated line to see which intake answer it came from. Builds trust in the output.
- Measure quality. Track "accepted as-is" vs "edited" vs "deleted." That ratio tells you if the AI is saving time or creating more work.
- Fallback: If AI fails, show a blank brief template with guiding questions. Never show an error. Show a tool.
Growth
Designs systems that bring users in and keep them coming back. The Growth Consultant looks for natural viral loops, acquisition leverage, and retention mechanics, building flywheels that compound rather than campaigns that decay.
Key Questions
- What's the organic distribution channel for this launch?
- Where does the best audience for this work already live?
- What makes someone share this project with their network?
- What's the built-in referral mechanic: what does a happy client do next?
- What creates compounding visibility over time?
Delivers
Example Output
Built-in distribution loop:
Every case study published on the new site is a standalone piece of content. Each one answers a specific search query: "brand refresh for SaaS startup," "agency website redesign process," "how to brief a creative agency."
- Case studies shared on LinkedIn reach the agency's exact buyer: founders, marketing leads, heads of brand
- The portal experience becomes a differentiator in pitches. "You'll get your own portal with live updates and version-tracked deliverables." That closes deals.
- Happy clients share the case study link when recommending the agency. It becomes the referral artifact.
Retention flywheel: The more projects a client runs through the portal, the more invested they are in the system. Case study history IS the relationship asset.
Optimizes the path from visitor to activated user. The Conversion Architect reduces decision friction, addresses objections before they arise, and ensures that every step of the funnel guides users toward their goal and the project's.
Key Questions
- What is the visitor's first question when they land?
- Are we answering it above the fold?
- Where are users abandoning the funnel and why?
- What objection is killing conversions and how do we handle it?
- What trust signal is missing at the decision moment?
Delivers
Example Output
Hero headline audit:
Before: "Creative work that drives results"
Answers nothing. Every agency says this. A visitor's first question ("is this the right agency for me?") goes unanswered.
After: "Brand and digital work for founders who need the vision to land. On time. On brief."
Three things the rewrite does:
- Names the audience (founders) in the first 4 words, self-qualifies visitors instantly
- Names the outcome ("vision to land"), not the service ("brand and digital")
- "On time. On brief." addresses the two biggest objections before they arise
Creates the flywheel beyond the project itself. Projects with network effects and community ecosystems outlast projects that don't. The Community Designer builds the structures that make users bring other users and make the project more valuable the more people use it.
Key Questions
- What would make past clients refer new clients actively, not just passively?
- What would make partner agencies recommend this team to their overflow clients?
- How does the portfolio become more valuable as more case studies are published?
- What can clients create or contribute to the agency's community?
- What's the developer or partner ecosystem opportunity?
Delivers
Example Output
Community play: Case Study Collaboration Program
Every published case study is co-authored with the client. The client gets a shareable, professional case study. The agency gets a distribution partner with a different audience.
- Clients share the case study in their own network. Referral radius doubles without paid effort.
- Top case studies are content that compounds over time. "Brand refresh for a Series A startup" ranks in search 18 months after publishing.
- Agencies who publish client-approved case studies build a public record of trust. That record is the moat.
- Over time, case studies become the primary sales tool. The community builds the pipeline.
Content is the portfolio. The client relationship builds the reach.
Innovation & QA
Sees around corners. The Innovation Director challenges shared assumptions, spots emerging shifts before they're obvious, and identifies category-defining moves that competitors will take years to copy, if they ever do.
Key Questions
- What assumption do all competitors share that might be wrong?
- What will users expect in 3 years that no one offers today?
- What would a 10x better version of this project look like?
- What emerging technology changes the rules of this category?
- What could we build that no competitor could copy quickly?
Delivers
Example Output
Shared assumption in creative agency websites:
Agency sites are portfolios of finished work. Every competitor (big or small) shows the same thing: beautiful images, brief case studies, a contact form.
The challenger question:
What if the primary unit was process transparency?
Every project has a beginning, a set of decisions, and a visible outcome. What if clients could see not just the result, but the decision-making that got there?
Category-defining move:
A Decision Log published alongside every case study: "We chose this direction because...". "The client pushed back here, and it led to a better outcome." Structured: Decision, Rationale, Who, When, Outcome.
When a prospect reads a case study, they're not just evaluating work. They're evaluating judgment. No agency publishes their reasoning. The one that does becomes the most trusted in its tier.
Catches everything before it ships. The QA Lead reviews the project through every lens (usability, accessibility, branding, performance, edge cases) and surfaces blockers before they become user problems or brand damage.
Key Questions
- Have we tested the empty state and the 404 state?
- What happens if a client uploads a file that exceeds the portal limit?
- Does this work on an iPhone SE and a 4K monitor?
- Is every interactive element keyboard-accessible?
- Does the site look and sound like one team built it?
Delivers
Example Output
🚫 Launch blocker, severity: high
The contact form "Send message" button is disabled until all 5 fields are complete, with no indication of which field is missing. On mobile, the validation error appears above the viewport. The user submits, nothing happens, and there's no visible reason why.
Impact: Contact form is the agency's only conversion point. A silent failure at the last step loses exactly the prospects who were ready to reach out.
Fix: Inline validation on blur for each field. Error text below the field, not above the form. Button stays enabled: failed submission shows a clear summary of what's missing.
Not a blocker to flag after launch. A blocker to catch before it. That's the QA mandate.