Creative Design and Project Management with Greg Storey
Designers and project managers bring different strengths to the same delivery. This episode summary explains how to combine creative judgement with planning, communication and shared accountability so design work meets business and user needs without losing room to explore.
Who is speaking and why it matters
Greg Storey, COO of LexBlog and a long-time design leader, discusses working with Brett Harned. Before LexBlog, Storey held design leadership roles at IBM and InVision and ran his own design agency. The conversation is aimed at project managers leading design teams and at designers who manage creative work themselves. It covers where the design role sits in a creative project, which project-management skills improve design delivery, why communication matters, how to keep design reviews productive, and how to build buy-in through simple supportive questions.
Designers need project-management skills too
Anyone delivering work to a business needs basic project-management discipline: a plan with dates and steady communication. Silence invites other people to fill gaps with assumptions, often unhelpful ones. Designers should therefore plan and communicate even when no dedicated project manager is assigned. Framing design as delivery against business and user needs, rather than as a search for a masterpiece, also makes starting easier and keeps scope grounded.
Frame critique around the problem
A project manager can add most value by helping the designer set up the critique. Agree in advance on the problem under discussion and the kind of feedback sought. That structure prevents a review from becoming a page-by-page tour and helps participants respond to the decision in front of them. The same coaching stance applies more broadly: be a coach, not a time tracker, and use questions that reveal what support the designer actually needs.
Build empathy and shared ownership early
Friction between project managers and designers is a central theme. Designers may resent project managers when the role feels like surveillance of time rather than help with delivery. A short early exercise counters that: ask what makes the project fly and what would blow it up, then record who is responsible, accountable, consulted and informed in a RACI. For teams running many projects, add a regular open-mic session and explicitly teach planning and communication skills that experienced project managers use by habit.
| Moment | Do this | Avoid this |
|---|---|---|
| Project start | Agree a RACI and ask what helps or could derail the project | Assume ownership is understood |
| During delivery | Keep a dated plan and communicate regularly | Let silence create bad assumptions |
| Design review | Frame the problem and the feedback wanted | Tour the page without a decision focus |
| Ongoing support | Coach, ask supportive questions and hold open-mic sessions | Act only as a time tracker |
Checklist derived from the episode takeaways; use as a working aid, not as a transcript.
Frequently asked questions
What project-management habit should designers adopt even without a project manager?
Treat design as delivery against business and user needs, keep a dated plan, and communicate frequently so silence does not turn into mistaken assumptions.
How should a project manager help frame a design critique?
Start from the problem and the specific feedback you want, rather than walking reviewers through every page. That framing makes critique focused and actionable.
What exercise helps a project manager and designer align early?
Act as a coach rather than a time tracker. Run a short exercise on what helps the project succeed and what could derail it, then agree a RACI at the start.
How can teams support designers who are juggling many projects?
Give designers a regular open-mic session and teach the communication and planning skills that project managers often take for granted.