in designing minimum viable products,
applying lean UX principles
kok.chiann@ezypay.com | 12.6.2013
UX
Hi, my friends call me KC
UX manager at Ezypay/iconnect360
Lead product design & user research
Manage multidisciplinary teams
Microsoft MVP since 2009
Some background
before we jump into the juicy bits
These were our past products
Design is not something we have been
good at in the past.
We have this huge, ongoing project
• That took almost 7 years and is still counting
• To replace our current billing system that cannot
scale to meet our business needs
• It meant replacing our customer service system,
billing engine, secure site, basically everything.
Today, let’s talk about the redesigning the Ezypay Secure
Site
It’s basically a portal where our clients can manage their
direct debit customers, do variations and get reports
Then…
We rebuilt this
secure site
twice, but we
never seem to
get there
We got on-
board a new
chief architect
from Silicon
Valley
He convinced
the business
to rebuild this
product, again
We knew we
had to do
things
differently to
ship
We got this out after 3 months
What did we do
differently
and what did we learn
Getting out of the delivery business
• We only relied on internal domain knowledge
• “Just enough” requirements & prototyping
Personas
• Priceless in scope management and prioritisation
SolutionProblem
Solution-based thinking
• We stopped rebuilding what is there, stepped back and
understood the problem and reconsidering the solutions
we have
As an administrator, I want
to increase or reduce the
amount of my customer’s
next direct debit
Edit debit
Add additional payment
Remove additional
payment
Collaboration & Alignment
We were all on the same page on our target users, MVP and deadlines
Everyone felt more empowered as they are involved in the design
We got more innovation – E.g.: A new way to handle outstanding payments
Design Workshops - Workshops
with BAs, UI/UX designers,
Developers, QAs and Instructional
designers to kickstart the design of
the customer page, as it is the very
core of the secure site product.
Review Sessions - All roles are
involved in the user story reviews so
everyone is on the same page.
UX governance
• MVP doesn’t mean we can ditch UX
• Usability first, Aesthetics second
• Reaching healthy compromises across business priorities,
user needs and technology (Grounded based on your
target users, minimum viable scope and deadlines)
Validated learning
• We did user testing on our initial versions.
• Stuff we thought were really important, aren’t
• We uprooted many issues we never expected. E.g.:
Disabled save button
• This guided the prioritisation of our iterative
improvements
This is what we covered
Getting out of
the delivery
business
Personas
Solution-based
thinking
Collaboration &
Alignment
UX governance
Validated
learning
That’s it folks!
More than happy to answer
questions or catch-up later
kok.chiann@ezypay.com
kokchiann.com

UX in designing minimum viable products, applying lean UX principles

  • 1.
    in designing minimumviable products, applying lean UX principles kok.chiann@ezypay.com | 12.6.2013 UX
  • 2.
    Hi, my friendscall me KC UX manager at Ezypay/iconnect360 Lead product design & user research Manage multidisciplinary teams Microsoft MVP since 2009
  • 3.
    Some background before wejump into the juicy bits
  • 4.
    These were ourpast products Design is not something we have been good at in the past.
  • 5.
    We have thishuge, ongoing project • That took almost 7 years and is still counting • To replace our current billing system that cannot scale to meet our business needs • It meant replacing our customer service system, billing engine, secure site, basically everything. Today, let’s talk about the redesigning the Ezypay Secure Site
  • 6.
    It’s basically aportal where our clients can manage their direct debit customers, do variations and get reports
  • 7.
    Then… We rebuilt this securesite twice, but we never seem to get there We got on- board a new chief architect from Silicon Valley He convinced the business to rebuild this product, again We knew we had to do things differently to ship
  • 8.
    We got thisout after 3 months
  • 9.
    What did wedo differently and what did we learn
  • 10.
    Getting out ofthe delivery business • We only relied on internal domain knowledge • “Just enough” requirements & prototyping
  • 11.
    Personas • Priceless inscope management and prioritisation
  • 12.
    SolutionProblem Solution-based thinking • Westopped rebuilding what is there, stepped back and understood the problem and reconsidering the solutions we have As an administrator, I want to increase or reduce the amount of my customer’s next direct debit Edit debit Add additional payment Remove additional payment
  • 13.
    Collaboration & Alignment Wewere all on the same page on our target users, MVP and deadlines Everyone felt more empowered as they are involved in the design We got more innovation – E.g.: A new way to handle outstanding payments Design Workshops - Workshops with BAs, UI/UX designers, Developers, QAs and Instructional designers to kickstart the design of the customer page, as it is the very core of the secure site product. Review Sessions - All roles are involved in the user story reviews so everyone is on the same page.
  • 14.
    UX governance • MVPdoesn’t mean we can ditch UX • Usability first, Aesthetics second • Reaching healthy compromises across business priorities, user needs and technology (Grounded based on your target users, minimum viable scope and deadlines)
  • 15.
    Validated learning • Wedid user testing on our initial versions. • Stuff we thought were really important, aren’t • We uprooted many issues we never expected. E.g.: Disabled save button • This guided the prioritisation of our iterative improvements
  • 16.
    This is whatwe covered Getting out of the delivery business Personas Solution-based thinking Collaboration & Alignment UX governance Validated learning
  • 17.
    That’s it folks! Morethan happy to answer questions or catch-up later kok.chiann@ezypay.com kokchiann.com