Slides from my talk given at Style and Class at Hootsuite on Monday, 11th July 2014.
This talk focuses on the struggles of maintaining a good design process whilst working in an Agile development environment. I explore the concept of the Agile Fog of War, which in essence is about the levels of fidelity we can work in to create a clear vision for our product's design. It's also critical to understand that working at these varying levels of fidelity that we keep our cost of change low to ensure we remain lean and agile with our decision making.
I also throw in a couple of techniques that we use at Mobify (http://mobify.com) to ensure we keep making valuable decisions the whole way throughout our product design process.
18. 2 Week Sprint
Personas
User Flows
Information Architecture
Wireframes
Prototypes
User Testing
Mockups
Implementation
(HTML & CSS)
User Testing
Review
Validation
60. Scope
Explore User Flows as much as humanly
possible
Develop Information Architecture for
every known object
Begin to define new features
Smaller concern for technical
implementation
Low Fidelity
61. Scope
Map Critical Paths and attempt to
account for as many states as
possible within those paths
Accommodate entry points to
features that you aren’t committing to
developing just yet.
Tighter collaboration with developers
to address implementation
Medium Fidelity
62. Scope
Mockups designed to give front-end
developers a precise expectations of
what each page/state should look like
Avoid scope creep. Functionality can be
reduced to hit shipping targets.
Features are shippable and usable
Tight collaboration with developers to
address implementation
High Fidelity
71. High Fidelity
Medium Fidelity
Low Fidelity
Personas
User Flows
Information Architecture
Wireframes
Prototypes
User Testing
Mockups
Implementation
(HTML & CSS)
User Testing
Review
Review
UI
UX
91. “Change is your best friend. The more
expensive it is to make a change, the less
likely you'll make it. And if your competitors
can change faster than you, you're at a huge
disadvantage. If change gets too
expensive, you're dead.”
!
- 37 Signals, gettingreal.37signals.com 2009
105. Title Text
Developer Setup Legend Adaptive.js
Customer
Touchpoint
(Email)
Last edit: Monday, March 24 at 11:23
Preview Bundle
Push First
Bundle
Inspect Bundle
Publish First
Bundle
Install Tag Verify TagDocs
Verification Error
Tag
Installed?
No Yes
Successful Publish
Tag Settings
Setup Local
Project
Create Project
Setup
Documentation
Get Slug/Init
Command
Generate Scaffold
Slugs need to be
exposed
send to device
open in new window
Locally
“View on localhost”
useless
Notification sent Via
Email/Web Push
Notification
Publish in Progress
Review Automated
Testing Results
Task
Supporting Input/Action
Task External to Cloud
Develop Bundle
Locally + Github
URL
Site Name
Download Bundle
1 First Time Only
Get Tools
1
npm install instructions
Download “Client”,
Grunt, Yeoman
Download
Adaptive.js
Windows
OS X
Linux
View Documentation
Get API Key
Developers are less likely to setup or even use cloud at all if they are working
on a large team with Producers/QA. Smaller teams however would mean the
developer is responsible for everything.
107. Title Text
QA Setup Flow Legend Adaptive.js
Customer
Touchpoint
(Email)
Last edit: Monday, March 24 at 11:23
Add other QA
Members to Project
Setup Local
Project (via
Github)
Login via Console
Pull Branch from
Github
Preview locally
Push Bundle to Cloud
Inspect Bundle
Get URL for Device
Preview
Site URL
Mobify Preview
(Visible to Client)
Bundle Location
Domain
Mobify This/All Tabs
Authorize
Install Tools
1
npm install instructions
Download “Client”,
Grunt, Yeoman
Download
Adaptive.js
Windows
OS X
Linux
View Documentation
Get API Key
Push Bundle
QA usually has to setup permissions for their own team members. The tag
will be installed for them but they will be making changes to the path.
They will never be publishing during the setup of a project, that usually
happens later in the QA process. They are more likely to send out a preview
for the client.
Review Automated
Testing Results
112. If you don’t know how, get a
developer to help you.
113. Even better, get them to set you
up with a GUI like Sequel Pro
www.sequelpro.com
114. Title Text
Information Architecture Legend Adaptive.js
Customer
Touchpoint
(Email)
Last edit: Monday, March 24 at 11:23
Inspect Bundle
open in new
window
Download Bundle
Automated Test Results
Download ToolsList Team Members
Install Tag
Verify Tag
Verification
Error
Add (Push) Bundles
Tag
Installed?
NoYes
Configure
Publish in Progress
Bundles Analytics (Future) Team
Publish
Preview
Delete
List Bundles
Invite Members
Remove Member
send to
device
Inspect Member
URL
Site Name
Tag Proxy
Modify Role
Get API Key
Delete Project
Tag
Manage Google Analytics
(a.js)
Set Device Support
Manage Targets*
Verify Tag
Unpublish
Notification sent Via Email/
Web Push Notification
Link to Docs
Link to Docs
Tag Verified
Verification Status
Link to Manage Organization
Get Slug
115. The more that your Information
Architecture can be mapped to the
data model the more likely it is that your
users will understand your application.
122. Focus on real data/content, or at least as
close to real as possible.
123. Focus on real data/content, or at least as
close to real as possible.
Every time you use Lorem Ipsum a content
strategist somewhere drops dead. No Joke.
126. Little thing that we do
Use a tool that lets us
wireframe and create
clickable prototypes
127. Wireframes can easily be made to be
interactive and clickable. Downside is it’s in
PDF format, not on the web and hard to
collaborate and annotate.
We use Omnigraffle
128. There’s plenty of other similar tools, just find
the one that’s best for your needs.