Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
bounded rationality
individual methodology
access through learned + interpreted schemas and heuristics
leap of faith
individual creativity
individual creativity
leap of faith
leap of faith
co l l a b o r a t i o n
for problems with compounding complexity
requires protocols for disagreement and a desire for a common ground
organizational politics
protocols for debate, mediation, and issue resolution
governance
boundaries for disagreement
desire to focus on the problem, mutual respect, motivation to make progress, a general agreement about the problem solving sequence, and egolessness
project issues
debate, discussion and argument towards agreement
brand rules
client identity forces
Fluid Process
Understand that problems can be wicked. Map existing patterns to problem and
select activities from situation, team capabilities, budget, constraints and input accuracy.
Be proactive and flexible enough to change with the problem.
disagree
Satisfice
Know that anything more than ‘good enough’ is
impractical and pick tasks that maximize action.
Know when to stop and move on to the next useful activity.
think Shared Understanding
Suspend disbelief to seek true values and opportunities by egolessly
and objectively investigating business, technical and audience needs.
Come to an agreement about a clear & collective problem definition
through the creation of visual decision making artifacts.
audience
constraints ↘ “good enough”
o p p o rt u n i ty
idea, market, blue sky
possibly a wicked problem
→ business
constraints → → → → o u tp u t
product, service or solution
technical
constraints ↗ early & often
Visual Language
Build or endorse a brand language for the project.
Learn and utilize the brand character and rules of combination
and grow the depth of the brand with the depth of the solution.
This fosters quicker adoption through building support over time.
ego
personal identity forces
A Note About Collaboration The difficulty of fluid collaboration is that everyone in the organization needs to have an impassioned They can no longer strictly sit inside the task and rely on the process to carry them through. Instead the
understanding of how to solve a design problem regardless of a particular process. The problem solver designer must become fluid moving freely between thinking and making as each new situation
must be confident, assertive, inquisitive, pragmatic, empathetic, and passionate. Each designer must emerges. And ultimately, the designer must learn to use visual decision-making as a way of presenting
value themselves and their opinions but also be respectful of the opinions and experiences of others synthesized thoughts to generate a response—disagreeable or not.
on their team. They must not only understand how to execute on tasks but they must be able to rise out
of a task and look holistically at the problem considering all parts of the system from the business
issues to people management to production requirements.
Name - Be meaningful, memorable, future-proof, protectable, positive, visual. Types: Founder, Descriptive, Fabricated, Metaphor, Acronym, A combination of
Value line - What is the end benefit to your customer? Types: Imperative, Descriptive, Superlative, Provocative, Specific
Pain Point - Who is the customer and why are they suffering?
Purpose - Demonstrate the value of the company by describing how you make the customer’s life better, where you product fits in the market; tell a story.
Business Model - Freemium, Subscription, Service, Product, Ad-Supported, etc Pile of Money - How big is the market and how much of it can you get?
Pricing - Who is going to pay for what, how often and for how long? Lifetime value - What is the lifetime value of a customer?
Product Line Up - Illustrate the what your making, major features, it’s system/architecture; make me believe it can be real.
Product Description
Product Features
Product Description
Product Features
Product Description
Product Features
Product Description
Product Features