Slides presented at Mozilla. They define kwamecorp's mission, how design and code work together, how we see open design and a new open index for projects we do.

1. Designing
in the Open
9 April 2013
Font used Adelle Sans Thin
Time to develop this presentation: 198 minutes
Conversation started at Mozilla offices — London
CC license 1.0 for this presentation

2. kwamecorp is
a social
enterprise
All our dividends go into the
creation/investment of more
projects for more positive social
impact

3. we work as two entities
R&D Lab Private equity
working for fund that
&
very large invests in ideas
corporations (start-ups)
= =
0.0 to 1.0 open index 1.0 to 3.0 open index
We’ll explain these numbers in the end

4. What we do @kwamecorp
Strategy Concept Prototype Development
It’s never truly linear but the
goal is to release products/
services that have a
positive impact in people’s
lives.

5. What we do, simplified
Value proposition Value reality
it’s all about validation and
the best way to validate is
to prototype quickly in
native environments

6. Our only purpose is
to add value to the
user
Positive impact

7. This means everyone
in a project keeps
their focus on one
thing:
Adding value to end users

8. PMs, Designers,
Coders... all busy
applying their skills,
but all share a vision:
Adding value to end users

9. Action point:
Define value
proposition that can
be broken down into
small parts and
validated
Strategy Concept Prototype Development
and yes, value propositions change, but
usually after they are validated

10. 1.
The value proposition needs to
be simple.
2.
Value proposition does not
change until it is validated.
3.
Value proposition is the glue
that keeps everyone in check.

11. The big question
is
Does open design
create a better
product?

12. If we take these two approaches
Idea Product/Service
Closed design
Idea Product/Service
Open design

13. Which one will add
more value to the
end user?

14. 1
Open ≠ Innovative
We work on some secret stuff that is
not less innovative

15. 2
There is no such
things as fully open or
fully closed design
Action point: assess the Open index
of a project before you start

16. 3
We do know that
Open design == more conversation
&
conversation leads to more learning
&
more chances to cross pollinate.

17. So how to make
Open design add
more value to users
than closed design?

18. First you need to
understand our
universe and its
players

19. Our universe looks
like this from the
outside

20. 1. Core has been
open for a long
time, loads of
UI
conversation
around it.
A meritocracy of UX
coders. 2. Design layers
appear open
because they are
Code visible. Reality:
UX / UI has
always been very
closed because
it’s not as
objective as
code.
Subjectivity
prefers closed
environments.

21. In fact, our universe
is more like this

22. We marry design and
coding in triangles
which are validated as
quickly as possible
Code
UX Validate
UI
Strategy Concept Prototype Development

23. Triangle serves to:
1. Show, don’t tell. Play.
2. Make sure everyone is aligned in the value proposition.
3. Validate.
Code
UX Validate
UI

24. This means designers
need to become
more objective
and more focused on validation
coders have been for a while

25. Many different players involved. All have egos, desires...
1. Make triangles cycles shorter.
2. The shorter the more focused and objective.
3. The more focused the quicker the validation.
Code
UX Validate
UI

26. Open design questions
Code
UX Validate
UI
Must the 3 atoms be open so
that we can add more value to
the end user?
Which one is easier to open first?

27. Design and code
conversations should
be around value
proposition

28. because when you
open a conversation
to everyone it
becomes very noisy
The issue becomes how to manage noise

29. Coders have
meritocracies and a
much more value
oriented approach
they have been doing it in the open for years

30. Designers don’t. They
tend to be less
objective.
not focused on value to user

31. How can designers
open their process
up?
when? How?

32. Well first they need to come to grips that
Design is NOT the
beginning NOR the
end of the process

33. The beginning is
value proposition
Code
Design is one of the
tools to get there
UX Validate
UI
The end is value
reality

34. So,
what should
designers open?

35. Value proposition
is
translated into feature sets.
Open feature sets up
for discussion. Invite
solutions.

36. Don’t open up initial
value proposition.
Your goal is to validate it through
feature sets. Agree on those and
open them up to collaborative
approach.

37. Fear
noise
but don’t panic
have a strategy

38. Be certain that
Openness does not kill
differentiators
&
You are not going to get less
competition because suddenly
everyone is collaborating

39. Ok, now for a
conclusion

40. If you mix the Anatomy of projects
public stuff happens
Beginning End
private stuff happens launch

41. With
Lawrence
Lessig’s
learnings from CC
creative commons

42. we came up with a Taxonomy of design
openness in projects
Closed
0.0
Open in beginning
and end
1.0
Open in beginning
and end, and
punctually 2.0
between
Open 3.0

43. Applied thesis
to kwamecorp projects
----

44. Fairphone OS
2.0

45. Impossible.com
2.0

46. BOND
2.0

47. S Educate
Khan Academy
1.0

48. Frameblast
0.0 2.0

49. Touchwiz
SAMSUNG Galaxy
0.0
Wonderful work but no conversation
(well it’s internal)
Would be great to share value
propositions though.

50. Curious fact:
In all that has been said,
the most practical tool
(beyond our validation
process) in opening up
our design process has
been Dropbox.

51. Join us for a conversation
@ our London Soho
showroom
94 Berwick st.
It’s open.
@kwamecorp

52. Thank you
info@kwamecorp.com