What are the 4 P's of design?
Written by
Passionate Designer & Founder
The 4 P's of design are Problem, People, Process, and Product. Most versions you'll find online treat this as a branding exercise. Used properly, these four categories are a diagnostic tool for figuring out where a design project broke down, or why it's about to.
Problem is the brief, but sharper. Not "redesign the onboarding flow" but "users are dropping off at step 3 at a 68% rate and we don't know if it's a copy problem, a trust problem, or a UX problem." A vague problem statement produces vague design. The best briefs I get from agencies we work with as a design partner define the problem in terms of a user behaviour or a business metric, not an aesthetic preference.
People means both users and stakeholders. In a design partner context, we're often designing for two audiences at once: the end user who interacts with the product, and the agency client who needs to present the work internally and get it approved. Ignoring the internal stakeholder audience is one of the most common reasons good design gets killed in approval cycles. On a McKinsey workstream we delivered, the output was technically a client-facing presentation, but the real "user" was the McKinsey partner running the meeting. Designing for that room changed every layout and typographic decision we made.
Process and product: where most agencies get the balance wrong
Process is where most agencies have the biggest gap. A defined design process is not a timeline. It's a sequence of decision gates: research, concept, direction alignment, production, review, handoff. Each gate has a binary output: proceed or restart. Without defined gates, revision cycles are infinite and nobody owns the decisions. We run a four-gate process internally, and that structure is the main reason we can turn around senior-level work in 48 hours without quality slipping.
Product is the artefact: the finished design, the delivered file, the shipped component. Teams that over-invest in process and under-invest in production quality end up with beautiful workflows and weak work. The product is what the client presents. The product is what the user touches. Everything else is scaffolding, and scaffolding doesn't ship.
The honest tradeoff with frameworks like this: they're only as good as the discipline around applying them. An agency that treats the 4 P's as a checklist gets checkbox outputs. The ones that use it as a diagnostic, asking "which P broke down on this project?" in the retro, build compounding quality over time. I've seen both. The difference in output quality after six months is not subtle.
For agencies thinking about how this maps to a design partner engagement, a good partner brings their own process to your workflow rather than absorbing your existing chaos. The web design agency process page covers how that works in practice. If you want to see how we apply this on live briefs, book a 20-min intro and we'll walk through a recent example.
Related guides: product design vs UX design
Related guides: design agency vs design subscription · design retainer vs design subscription · design partner for agencies · design production partner
