Why to analyze users' needs

User Centered Design

Different companies have different ideas, needs and resources. Without a good analysis the expectations and the result diverge and the client gets something he did not want for money he does not have.

  • Client: Clientigent
  • Date: September 2021
  • Style: Hand-drawn

Main ideas

Before a custom software is built, the users’ needs have to be analyzed.

  1. Different companies have different ideas, needs and resources.
  2. Interviews with stakeholders about their needs and expectations.
  3. Then the goal, price, deadline, … are clear and problems are prevented.
  4. Otherwise the expectations and the result diverge and the client gets something he did not want for money he does not have.

Script

The theme is making a custom ceramic teapot – first the wrong way, then the right way.

  1. Different ideas – the client needs a teapot for tea (15 s)
    • the client imagines pouring tea from the teapot into a cup (thought bubble)
    • the client tells the guy his requirements (speech bubble): the pattern on the teapot, its volume in litres, the shape of the spout
    • a checklist of requirements forms under the guy, the information moves from the bubble to the list
  2. Without analysis – he gets what he wanted, not what he needed (20 s)
    • the guy calculates the size of the teapot from the volume, 4/3·π·R³ ⇨ R
    • a round teapot with a narrow spout and without a handle is drawn (build), the client looks at the clock
    • a flame is drawn under the teapot and steam comes out of the spout
    • the missing handle blinks, the client grabs the teapot and burns his hand (it grows and shrinks)
    • the tea does not pour from the spout, it only drips
    • when the client puts the teapot down, it rolls over and the tea spills
    • finally the guy tells the price and the client’s monocle falls out
  3. With analysis (15 s)
    • the guy asks the client about all parameters, the whole teapot is drawn in the speech bubble and the camera zooms on the part being discussed, which changes several times:
      • price (a slider from $ to $$$)
      • deadline (a calendar, a day is ticked)
      • volume (bigger/smaller)
      • shape of the teapot
      • type of the handle
      • width of the spout
      • shape of the lid
      • pattern on the teapot
  4. It turned out well (10 s)
    • the client has the same idea as at the beginning and the guy gives him a teapot which is exactly the same
    • the agreed date is on the tear-off calendar behind the client
    • the agreed price ($$) is on the teapot
    • both the guy and the client smile
  5. With good analysis (5 s)
    • ✓ meets client’s needs and goals
    • ✓ meets terms and dates
    • ✓ meets budget and costs

Storyboard

Storyboard