Making Stakeholders App Designers Instead of Architects

© outsystems – all rights reserved www.outsystems.com

Making Stakeholders

App Designers

Instead of Architects

http://bit.ly/stakeholderdesigners




spend time modeling the real life to something that

only he understands... inside a black box

meet The Developer

blog.teamtreehouse.com


vinylgs.com

development team forgets the real life

and just talk in a model language


Stakeholders “just” know real life

on the other side...

They own the business context


Stakeholders try to model the real life expecting

this way developers will understand what business

needs

Common Mistake?


Where the apps

are Great!

Developers confort

zone


Here’s your

framework to

get your great

apps!

How to end with the gap between

stakeholders and developers?


Steps to get your great app

# 1 - Understanding the user

# 2 – Designing the app

# 3 – Testing

# 4 – Monitoring


#1 Understanding the user

Context is everything,

create a user story.

• Improves communication

• Helps to learn the stakeholders “language”

• Capture the reason why we’re delivering something.


Stop asking...

• “ What functionality should the app provide?”

• “ The system needs these data elements to complete the function.”

...and start answering:

• “What is user’s primary goal in this scenario?”

• “As a sales manager, Peter Man, must have access to sales

pipeline in order to …”

User Story #1 Understanding the user


By understanding the

users, developers will

start thinking

differently


Where the apps

are Great!

Developers confort

zone

Progress so far


#2 Designing the app

What Info is relevant for the user?

How can the user achieve the goal with

less effort?


Information Architecture #2 Designing the app

An effective information architecture must reflect

the way users think about the subject


• Forget technology and

just solve the interface

problem.

• Figure out how to best

convey the message,

lead the user, present

the data, etc.

• Get a quick baseline in

your discussion with the

user and dev team

Sketch mockups #2 Designing the app


By knowing how users think

through the information

architecture and with the

baseline for discussion with the

interface mockups, half of the

way for a great app it’s done.


Where the apps

are Great!

Progress so far

Developers confort

zone


#3 testing

Testing it’s not just a bug search activity

buzzle.com


Usability Tests #3 testing

Usability tests start during the first Demo

• 1st reactions are the most genuine

• Usually there’s Feedback...tons of it

• You don’t need extra budget to this

Why is so important developers participation?

Disclaimer: this doesn’t substitute user experience tests during the project, it’s another

activity to reach the goal of great apps.


Acceptance tests #3 testing

• Create the acceptance criterias for top user

stories

• Setup an environment with realistic sample data

• This will help your business realize what they

really need you to deliver

Do test it!


Where the apps

are Great!

Developers confort

zone

Progress so far


#4 Monitoring

• Performance, errors, utilization, “cool” new

features in the platform for this but

don’t forget users feedback

• Embedded Change Technology

• Collect feedback for Usability quick wins


Where the apps

are Great!

Developers confort

zone

You both did it!!


Wrap up

• # 1 - Understanding the user

– Don’t model reality

– User stories written with concrete business value

• # 2 - Design the app

– Design information architecture

– Use Mockups for the top user stories

• # 3 – Testing

– Both teams should participate in Demos

– Acceptance tests

• # 4 – Monitoring

– Feedback


Start getting those

great apps today!


Thank You

[email protected]



Making Stakeholders App Designers Instead of Architects

Technology

Transcript of Making Stakeholders App Designers Instead of Architects