6 Critical Points in the Design Process. Part 1.

gde.design process

Vision

This tricky thing is also called a briefing. Going down to the most elementary level, this is the initial vision of the product presented by the customer on one sheet of paper.

  • Why do your users need it?
  • What is the USP?
  • What is needed to create it, what isn’t required, where are we growing, what is the budget of the venture, how we measure success, etc.

🖖 How is the briefing useful for you and us?

In short, there is nothing more useful at this stage of development. It helps you see the goal and soberly assess whether you should fool your head with it. Your client also organizes global goals and resources, evaluates the scale of the venture, and analyzes the risks. In the language of business, they are starting to save money now.

⛔️ But what happens if you don’t have a briefing?

As for the money, everything is already clear. There is a risk of squandering the entire or almost the entire budget. As for time, you will lose it forever. That expensive time that could be spent on development will be mercilessly spent on a new strategy and redrawing 70% of the screens.

Development Plan

The Development Plan is a complete written list of the future product’s features with their term and priority, approved by you, the client, and the development team (if any). There are a thousand miles between the Vision and Development Plan stages, the first diamond of the Norman double diamond model, and the answer to the question “Are we actually creating what we invented?”

🖖 How is it useful?

You know exactly what, in what sequence and when should be done. Or not done. If your plans change or new features appear during further work on the project, they will be reflected in the development plan and shift all deadlines.

⛔️ What happens if you ignore the dev plan?

Well, first of all… Monetary losses, which are quite commensurate with losses from the non-creation of Vision since it is not clear what exactly we decided to do. In addition, there is a risk of incorrectly assessing the project, having a too optimistic, or, conversely, too pessimistic forecast for its development. Overly creative personalities can suddenly get carried away with creating new features at the prototype stage and deviate from the plan described only in their mind.

  • How are we doing?
  • Are we ready?
  • Why aren’t we ready yet?

User Flow

There are several ways to describe all possible application scenarios — from user stories and block diagrams to a highly detailed prototype. The most effective is a modernized user flow diagram both in terms of speed of creation and clarity. Unlike classic user flow, this is a hybrid of three documents at once: block diagrams, l-f prototype, and Data Model diagram fragments. Instead of text boxes, I create low-fidelity screens and add descriptions of data and functions to them, making them faster to read and easier to understand.

🖖 How is it useful?

User Flow is a squeeze-out of all your product architecture and user-friendly UX ideas, the first cut-off in UX design. It can be done in 1–2 weeks (about $ 200- $ 1200, depending on your rate). And it can be read and edited all at once. Right now, and not later, when a bunch of micro-solutions has already been drawn and implemented.

⛔️ What happens if you don’t do User Flow?

In the User flow phase, you create a global UX. There is no global UX — there is no skeleton on which you will then string micro features. Without a user flow, a designer spends threefold much time working out both local and global logic in a highly detailed prototype.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
gde.design

gde.design

We design products that bring millions. Individual UX solutions to fit your business goals.