Building a screen is one thing, but creating a seamless experience is an entirely different challenge. Over the years, I’ve gained a deep understanding of interface development—from ideation to design, implementation, and delivery. Along the way, I’ve seen common pitfalls that can slow teams down or create confusion.
To help streamline the process, I developed a simple framework called the “5 D’s.” It’s not about rigid rules but rather a way to bring clarity, align responsibilities, and set clear expectations so everyone can move forward with confidence. While the 5 D’s align with well-known design processes in the industry, the real focus is on fostering intentionality, collaboration, and thoughtful execution in everything we build.
Phase 1: Define The Problem
During this discovery phase, the entire pod collaborates to explore ideas and define problems. The deliverable is a Game Design Document (GDD) that outlines the feature request, emphasizing problem definition rather than being tied to a specific solution.
Phase 2: Design The Solution
Once the GDD is approved, the UX or Product Designer breathes life into the design, working collaboratively to refine and test various ideas. Wireframes are created, followed by UI Artists developing mock-ups that add fun and delight to the user experience.
Phase 3: Discuss The Implementation
With the design finalized, responsible parties come together to discuss and document implementation details. Engineers and Technical UI Designers sync to define the data contract and provide detailed estimates for completion time.
Phase 4: Develop The Feature
With clarity on the requested work, the implementation team assembles the interface, matching the mock-ups and styles. Each definition of done is completed and verified, ensuring alignment against expectations.
Phase 5: Deliver The Request
The team reunites to present the finished design, allowing for feedback and approval. Once approved, the task is considered complete, and the team moves on to the next one.
The 5 D’s provide a guiding framework to help teams align on a shared vision and clear definition of completion. To further reduce ambiguity, I put together a straightforward RACI chart that maps out who is responsible, accountable, consulted, and informed at each stage of the delivery process. It’s not about rigid roles - it’s a handy reference that bring clarity, supports collaboration, and even helps onboard new team members more smoothly.
Every "Phase" of the 5 D's aims to progress us towards the completion of a feature or request. Naturally, each feature may reside in different phases. To facilitate comprehension, we employ color-coded indicators for each phase in the development process.