Build it Right the First Time

An idea is only the beginning. Executing on it is 99% of the work.

This class is for anyone on a team who wants to build better web, mobile, or software applications. What's the secret? Clarity.

Slides from Skillshare Class:
http://www.skillshare.com/Build-it-Right-the-First-Time/1813552089/364608238

Transcript

1. Build it Right the First Time @rypan
3. what you’ll learn problem today is lack of clarity in product development a simple solution sits right in front of us: wireframes tools and techniques 10 crimes of dysfunctional teams
4. Ginger.io Customer & Product Various Startups Design Advisor CalTV Founder Salesforce.com Designer Microsoft Program Manager Outlook for Mac Program Manager Pipette Founder Funnel Founder a bit about me
5. all team sizes all stages
6. product timeline idea design development test release
7. idea design development test release excess bugs missing deadlines talent leaving falls short politics vNext competition frequent rework
8. WHY DO BUGS HAPPEN?
9. WHY DO BUGS HAPPEN? design development Weak start to a project Regular rework Saying done too early
10. WHY DO SCHEDULES SLIP? test release Uncertain path to completion Not enough visibility points Last minute additions
11. HOW DO YOU MISS THE TARGET? release idea not listening enough “obvious issues” lacking useful data
12. STARTUP VS. BIG COMPANY
13. idea design development test release excess bugs missing deadlines talent leaving falls short politics vNext competition frequent rework
14. clarity
15. |ˈklaritē| clarity the quality of being clear, in particular the quality of being certain or definite
16. |ˈklaritē| clarity the ability to keep everyone on your team on the same page
17. doing things faster building things better
20. wireframes are the new language
21. alerts photo sharing app notifications job finding app news feeds email alerts search engine push notifications corporate social network photo filters
22. alerts photo sharing app notifications job finding app news feeds email alerts search engine push notifications corporate social network photo filters text only goes so far
23. alerts photo sharing app notifications job finding app news feeds email alerts search engine push notifications corporate social network photo filters too many interpretations
24. JUST SKETCH IT
25. power of wireframes Icons by: Arjun Adamson, John Caserta, and Bernard Huang from The Noun Project
26. Twitter From Jack Dorsey’s Notebook
30. Ryan Panchadsaram PROFILE Posted a photo 5m ago
35. tools
36. tools
37. tools
38. ANY GOOD WAY TO APPROACH?
39. Goals MONEY USERS ENGAGEMENT REDUCING ERRORS PAGE VIEWS DOWNLOADS MOBILE USES VIDEO DESKTOP IS SOCIAL ACCEPTS PAYPAL LOOKS LIKE X USES TWILIO WORKS FOR 65+ HAS FILTERS ENCRYPTED FACEBOOK CONNECT USES GPS BUILDABLE TODAY PULLS RSS Attributes +
40. How do I share them with my team?
41. be in sync. use wireframes as the direction you are going.
42. use wireframes to keep everyone involved.
43. you are responsible for the rally.
44. lead your team. give your managers the tools to communicate upwards.
45. Using Wireframes Smartly
46. idea Partners, Investors, Management
47. idea conversations & meetings
48. design YOUR TEAM
49. design WIREFRAMES ARE THE CORE OF THE DISCUSSION
50. design TALK TO YOUR USERS. BUY THEM COFFEE. DON’T PITCH.
51. design SPEND MORE TIME LISTENING SPEND MORE TIME OBSERVING NEW PRODUCT EXISTING PRODUCT
52. development LEARN WHILE BUILDING
53. development visibility points corkboard user testing dogfooding demo days
54. development visibility points corkboard user testing dogfooding demo days you can do all of this today
55. WHAT DO I DO WITH WHAT I’VE LEARNED?
56. Forge Ahead Pivot Quit ?
57. Forge Ahead Pivot Quit ? paving forward is conviction. it can be brilliant. it can be stupid.
58. Forge Ahead Pivot Quit ? pivoting means you’ve learned something. sometimes it is big. you’re course correcting. sometimes it is small.
59. Forge Ahead Pivot Quit ? it’s okay. learn from it.
60. Forge Ahead Pivot Quit ?
61. IF I’M SMALL, WHAT DO I DO?
63. clarity just sketch it. use wireframes to communicate. involve your team. learn and listen to your users. make your progress visible. know when to make changes.
64. Break Time
65. 10 Crimes Highly Dysfunctional Teams Commit
66. 10 Crimes Highly Dysfunctional Teams Commit MOST
67. Working in silos 1 Design solutions together Find champions who understand Specs will never be perfect
68. Over-thinking, Over-designing 2 Conway’s Law Know the weight of your feature Aim for simplicity Share your work, you’ll learn fast
69. Saying Things Are Easy 3 Nothing great is easy Crafting experiences take time Never underestimate competition
70. Calling Hacks Complete 4 Use them as learning tools Encourage as exercises
71. Trying to Build for Everyone 5 A solution for everyone, is a solution for no one Know who you are building for Take a stand Do something incredibly well
72. Free for All 6 Only works in particular orgs. You vs. Someone Else There is a true north
73. Saying Yes 7 Be purposeful Say no. Draw the line.
74. Saying No 7 Be open to ideas You don’t want to be left behind Keep listening
75. It’s Been Done Before 8 Revisit existing ideas & solutions Today is a different day
76. Failing to Measure 9 Don’t fly in the dark Be smart and measure Try Mixpanel
77. Breathing Room for Creativity 10 Strive for inspired solutions Embrace your inner-geek 20% projects are really 120%
78. ten lessons 1 work together 2 aim for simplicity 3 great products take time 4 learn from hacks 5 take a stand for your user 6 know your product 7 learn when to say yes/no 8 build it again, differently 9 measure 10 allow creativity
79. fin.
80. now go sketch.