how to build successful digital products. · build resource models inhouse resources this is often...
TRANSCRIPT
How to build successful
digital products.
Why Create?2 main reasons:
1. Lead Gen
2. Value Add
3
4
5
6
7
Build v. BuyWhat makes sense for your project?
1
When to
BuyProducts already on the market may be
perfectly suitable to meet your needs
9
Options to buy your
products
10
11
12
13
When to
BuildSometimes custom is really what you need.
14
Primary Reasons- You need a custom
interface
- You have complicated data
needs
- You want to sell to others
- You need other
bells/whistles
15
What Does it Take?What roles are needed to create a successful product?
2
“Building Successful Digital
Products is Really, Really Hard!
17
What roles do you need?
Product/Project Manager UX Researcher/Designer Visual Designer
18
QA Tester Front-End Developer Back-End Developer
Build resource
modelsInhouse resources
This is often the most
expensive option if you’re
going to maintain a full
team
Outsource to Agency
Look at agencies with
expertise in the space or
with the technologies
you’re looking at using
Combination
Depending on the type of
project and the goals, this
may be the preferred
model for many
organizations
19
Respective Benefits and
LimitationsOf Insourcing v. Outsourcing
3
Strengths
Subject matter expertise
Understanding of clients
InsourcingLimitations
Time!
Lack of resources
Not knowing what you don’t know
21
Strengths
Ability to scale
Native expertise
Resources
Can teach processes that can be
replicated
OutsourcingLimitations
Lack of subject matter expertise
Over-reliance risks not building the
skills internally
22
Development Process
4
24
25
26
Define GoalsHow do we define success?
How do we measure that?
Empathy/DiscoveryUser research
User personas
29
30
IdeationDesign Thinking
Prioritization
32
33
ValidationPrototyping
Define and Test Assumptions
35
36
37
Design/Build
39
40
IterateTesting
Backlog Management
Things Nicole
wishes new builders
knew
42
● Understand your
goals/metrics for success
● Think about marketing
● Think about maintenance
● Validate!
● Design.
43
