Post on 02-Aug-2015
great examples of quality improvement
illustrate development of ideas and technology
but preservation of legacy
On one hand some designers believe that by discarding work of another guy or girl on a project they start revolution.
Most often not!
On the other hand some product owners believe that by simply adding more features they make their product better.
Most often not!
Assumptions to start with
• Technology changes
• Context changes
• Expectations change
• Ideas evolve
• You work on yet
another iteration
Therefore
• Think roadmap
• Think development
bandwidth
• Think evaluation
picture by unsplash @ pixabay.com
Steps to take to initiate a quality improvement
1. Study existing version first: purpose, history,
mechanics…
2. Get know users and their feedback’ feedback.
3. Find out what ideas development team has.
4. Read business requirements for the first time. All!
5. Analyze existing pain points and missing parts
to fix before new features can be developed.
6. Re-create
information
architecture and/or
screen flow.
7. Group new features
into categories.
8. Find an appropriate
place for new
features between
existing ones.
F1
F2
F3
F2.1F2.2F2.3
F4
F2.4
F4.1F4.2
F1.1
Sometimes you need to add not requested features to accommodate
requested ones.
picture by unsplash @ pixabay.com
Steps to take to make a quality improvement
8. Go through features list and sketch ideas
considering existing pain points.
9. List screens and functions that might be affected.
10. Be ready to revise screens at least twice.
11. Discuss proposal with product owner.
12. Discuss proposal with developers (de-scoping
follows).
13. Prepare semi-final specification, get approval and
share.