kwamecorp designing in the open

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.

Transcript

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. R&D Lab working for very large corporations = 0.0 to 1.0 open index Private equity fund that invests in ideas (start-ups) = 1.0 to 3.0 open index we work as two entities & We’ll explain these numbers in the end
4. Strategy Concept Prototype Development What we do @kwamecorp It’s never truly linear but the goal is to release products/ services that have a positive impact in people’s lives.
5. Value proposition What we do, simplified it’s all about validation and the best way to validate is to prototype quickly in native environments Value reality
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. Strategy Concept Prototype Development Action point: Define value proposition that can be broken down into small parts and validated and yes, value propositions change, but usually a er 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. Does open design create a be er product? The big question is
12. Idea Product/Service Idea Product/Service Closed design Open design If we take these two approaches
13. Which one will add more value to the end user?
14. Open ≠ Innovative We work on some secret stuff that is not less innovative 1
15. There is no such things as fully open or fully closed design Action point: assess the Open index of a project before you start 2
16. We do know that Open design == more conversation & conversation leads to more learning & more chances to cross pollinate. 3
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. Code UX UI 1. Core has been open for a long time, loads of conversation around it. A meritocracy of coders. 2. Design layers appear open because they are 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. Code UX UI We marry design and coding in triangles which are validated as quickly as possible Validate Strategy Concept Prototype Development
23. Code Triangle serves to: 1. Show, don’t tell. Play. 2. Make sure everyone is aligned in the value proposition. 3. Validate. UX UI Validate
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 UI Validate
26. Code UX UI Validate Open design questions 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. open a conversation to everyone it becomes very noisy The issue becomes how to manage noise because when you
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. Design is NOT the beginning NOR the end of the process Well first they need to come to grips that
33. The beginning is value proposition The end is value reality Code UX UI Validate Design is one of the tools to get there
34. what should designers open? So,
35. Value proposition is translated into feature sets. Open feature sets up for discussion. Invite solutions.
36. Your goal is to validate it through feature sets. Agree on those and open them up to collaborative approach. Don’t open up initial value proposition.
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. Beginning End If you mix the Anatomy of projects launch public stuff happens private stuff happens
41. learnings from CC creative commons With Lawrence Lessig’s
42. we came up with a Taxonomy of design openness in projects 0.0 1.0 Closed Open in beginning and end Open in beginning and end, and punctually between Open 2.0 3.0
43. Applied thesis ---- to kwamecorp projects
44. Fairphone OS 2.0
45. Impossible.com 2.0
46. BOND 2.0
47. Khan Academy 1.0 S Educate
48. Frameblast 0.0 2.0
49. SAMSUNG Galaxy 0.0 Wonderful work but no conversation (well it’s internal) Would be great to share value propositions though. Touchwiz
50. In all that has been said, the most practical tool (beyond our validation process) in opening up our design process has been Dropbox. Curious fact:
51. Join us for a conversation @ our London Soho showroom 94 Berwick st. It’s open. @kwamecorp
52. Thank you info@kwamecorp.com