Project Planning

The most important fact about a project is when it starts, it starts. when it ends, it ends. However it never is a straight-line journey and usually gets chaotic, but the best way to avoid this chaos is to plan. Proper prior preparation prevents piss poor performance.

Project Needs

A project will have it’s needs to ensure that is runs well, here they are:

The first thing you do with a client is you try and clarify what they need and what User Problem are we actually solving, so you work with them to find that out

You then need to find out who the team is, who is in it and what are their functions, if someone is a user researcher assign them to that role, if someone is proficient in Figma assign them to that.

You need to establish a goal/vision, what does success look like, for the team, for me?

Scope and constraints will need to be established, what is the budget, what are our resources, our timeline, what is in and what is out? Two Constraints with our project is Time and not being able to communicate with the end user

Scope creep is the uncontrolled, undocumented growth of a project’s scope beyond its original goals, so do whats in scope first, so if you have time you can do more.

Key metric are indicators for success, how will we know we’ve done it and how will we measure success?

Who are the Stake holders? Who Needs to be involved in this project? So think of this circle of core, important and helpful. So Core affect the Decisions, Important Help to keep us informed and Helpful are people to consult or learn more about the topic

The Frameworks

These are two frameworks for thinking

The Double Diamond

DD Diamond.png

So the Double Diamond is that every-time your in a discovery phase or developing phase it opens up the diamond, So the Discovery Phase is exploring the problem space through user research, observation, and data collection, Define is to synthesising insights to clearly frame the problem and establish a design focus

The Middle is the more you know about the problem, it is only before you know the problem and define it you can develop for it, so generating testing and refining multiple ideas to address the defined problem, then you deliver which entails implementing, validating and refining the solution based on real world feedback

Stanford D-School Design Thinking process

Then There’s the Stanford D-School Design Thinking process which is Empathise, Define, Ideate, Prototype and Test

Honeycomb.png