Process
//
Process //
Decoding Behavior Beyond Functionality
I guide you in developing products by analyzing various aspects of human behavior, such as psychological, social, emotional, and functional perspectives. While the final product – its functionality, rationale, appearance, and platform – is certainly crucial, the primary focus remains on meeting people’s needs. My guiding principle? Prioritize understanding human behavior over strictly adhering to functional specifications.
I have recently adopted the Squiggle methodology, as conceptualized and named by Daniel Newman. Essentially, it emphasizes that there is no one-size-fits-all process for innovation, as it doesn't follow a linear path. Instead, innovation often starts in a chaotic fashion and gradually finds clarity as it evolves. The key is to welcome and embrace this initial chaos.
Week 1
Our primary focus here is you. After initiating several collaborative sessions with your team, we aim to understand the problem at hand, identify our target audience, establish business objectives, and recognize challenges. Together, we’ll devise a solution that centers around human needs. Additionally, we’ll establish a collaborative framework, discovering the most effective ways we can work in unison.
Outcomes
Full comprehension of The Problem
Identification of Business Objectives and Challenges
Formulation of Problem Statements
Creation of Hypothesis Statements
Execution of Primary Research
Determination of Project Timeline
Clarification of Roles and Responsibilities
Assessment of Technical Constraints
Week 2
Here, our focus shifts towards the end-users. We’ll deeply immerse ourselves in understanding our users, unraveling their social, emotional, and functional necessities. As the week progresses, we’ll begin brainstorming features that adeptly cater to these identified needs.
Outcomes
Execution of Affinity Mapping
Conducting Lean UX Workshops
Identifying ‘Jobs to Be Done’
Creating User Stories
Formulating ‘How Might We’ Statements
Ideating Feature Concepts
Producing Preliminary Sketches
Week 3
Teamwork often outperforms individual efforts in design. While I maintain my role as the “designer”, providing expert suggestions and overseeing high-fidelity work, it’s crucial to understand that everyone on your team has an opportunity to take ownership of the product beforehand. This inclusive approach broadens our pool of ideas, fostering a more robust solution. Plus, it’s an enjoyable process!
Outcomes
Execution of Rapid Prototyping
Defining the Minimum Viable Product (MVP)
Creation of High-Fidelity Designs
Conducting Presentation and Critique Sessions
Establishing Brand Identity
Building a Design System
Week 4
At this stage, our designs are finalized and prepared for the next step: handing them off to the developers for construction. Throughout this phase, we’ll organize periodic reviews to monitor the work in progress and conduct quality assurance for the designs. We also provide the option to validate our designs through user testing, which could involve A/B testing or customer interviews after product launch.
Outcomes
Developer Handoff
Conducting A/B Testing
Performing Design Quality Assurance
Undertaking Design Re-iterations
Hosting Post-launch Interviews