GET OVER YOURSELF: COLLABORATION IS THE SECRET TO GREAT PRODUCTS

Let this sink in: 9 out of 10 startups fail. Among the most common reasons cited by company founders for these failures is that they didn’t have the right team.

What do you suppose are the underlying reasons that a team may not be right?

As a veteran project manager turned startup marketer, I’ve learned that the reason teams made up of highly intelligent and capable individuals fail, more than any other reason, is because of poor communication. Indeed, according to the Project Management Institute(PMI), ineffective communication can be attributed to 56% of failed projects.

“Teams that fail, fail to listen to each other.”

The Build–Measure–Learn loop emphasizes speed as a critical ingredient to product development. Often a focus on speed causes teams to devolve into a group of individuals focused on their own contributions rather than collaboration. This sort of myopic approach may yield a functional product—but it rarely yields a viable product.

Collaborative teams that listen to each other—and to their prospective customers—are more prone to create MVPs that are functional, reliable, usable, and emotive.

[圖片上傳失敗...(image-d3d036-1516269486111)], from the Design Agency Glossary.](http://upload-images.jianshu.io/upload_images/1690759-b02d3c4c0cd3fa7c.gif?imageMogr2/auto-orient/strip)

So then how can teams be intentional about collaborating? I’m so glad you asked…

Start by (and always be) learning—together

Most product teams have an idea and want to build something straight away. That energy is fantastic, but lean methodologies tell us that the purpose of early iterations is to learn as much as possible as quickly as possible. The goal is to test marketability of the idea in order to determine if you’re on to something. 4 ways to do that:

  1. User research. Understanding user behaviors, needs, and motivations is an essential first step to building a product that people want (or need). There are many user research techniques: interviews, card sorting, surveys, etc. Often designers are responsible for this type of research, but including others in the selection and execution of a research project will help create a shared understanding of the problem your team is solving.
  2. Personas. These abstracted customer archetypes are common deliverables for most product teams. Their focus may vary from team to team or product to product: understanding demographics may be important, or perhaps psychographics or something like technical skills may be more appropriate. One benefit of creating personas is an increased sense of empathy for users. Proto-personas are a great start because everyone can get in on the action.
  3. Paper prototyping. Some people argue that paper prototypes are a waste of time. But naysayers, agree that they are appropriate for early stages of the design process. Using paper and markers levels the playing field, allowing the whole team to participate in a conversation about possible UI solutions to the problems you identify in research. This also sets a great precedent for future design critiques.
  4. Define success. “How would you feel if you could no longer use [product]?” According to Sean Ellis, co-founder of Qualaroo, if 40% of customers answer “very disappointed” to that question then congratulations are in order. You have found product-market fit! Aligning on the definition of done can quiet arguments before they start, keeping team spirit high.

Build something collaboratively

Everyone involved in creating a product is a ‘maker’ of some kind. Each team member may specialize in a particular discipline (design, development, analytics or management), but that doesn’t preclude anyone from contributing to the entire process. Before you dive in and start designing your next mockup or coding a function, consider taking a collaborative approach. And remember, providing honest feedback to each other during these activities is one of the best things you can do for each other.

  1. Design mockups. Whether your tool of choice is Sketch or Photoshop, high-fidelity comps are subject to the an inordinate amount of subjective critique. To avoid a bevy of ungrounded feedback restate goals at the beginning of any critique and show prototypes (in InVision!) whenever possible. To avoid groupthink, participants should write down their feedback first and then discuss.
  2. Pair program. So not everyone on your team is able to code in Ruby. That doesn’t mean you can’t find for opportunities to make decisions in real time, together. Fine-tuning the easing of a CSS transition, choosing a menu configuration, or writing headlines are all activities are all great times to stop, collaborate, and listen.
  3. Integrate analytics. Before releasing any product into the wild be certain that goals are mutually agreed upon and key events are tracked. Having analytics in place will give your team important information with which to make decisions about future features to help achieve product-market fit or scale your business. Using an analytics API like Segment can make everyone’s job a little easier because it simplifies implementation and provides turnkey access to other tools.
  4. Quality assurance. Testing is an essential part of building great software. Sure, developers writing unit tests can be helpful, and automation speeds things up. But nothing can replace manual testing. Each person on the team shares responsibility for what gets shipped. Everyone is a quality ambassador.

Measure how you did, collectively

Even the most data-driven teams have to make a lot of assumptions and guesses to ship a product. The best way to mitigate missteps is to assess the efficacy of those decisions along the way. 2 ways to do that:

  1. Usability testing. One of the best ways to improve a product is to get feedback from representative users—millennials may understand your product better than a senior business executive. Online user testing services make problem discovery a whole lot easier by making thousands of test subjects accessible to you, so those problems can be remedied before releasing the product to the wild.
  2. Split tests. Eliminate lengthy debates about which design solution is best by A/B testing. Optimizely makes it easy to collaborate on split tests because it makes it easy to explore many ideas. Everyone gets a say, and the best-performing option wins. No egos, just results.
  3. SQL. Advanced analytics is one of the best methods of identifying cause:effect relationships between the customer experience and business performance. Sit together to ask questions, write queries, and find answers. You’ll be amazed at what you can unearth through collaborative analysis.

Iterate, because “good enough” never is

Teams must work together to incorporate validated learning into each and every aspect of their work. As the marketplace changes, products and marketing should be modified to better meet customer needs. Here are a couple of activities your team can do to inform the next iteration of your product.

  1. Net promoter score. “Would you recommend this product to a friend or colleague?” That simple question is an invaluable indicator. Knowing which customers are promoters and detractors helps marketers generate case studies and product teams better understand their ideal customer. I’ve found Delighted to be a great tool to capture this information.
  2. **Cohort analysis. **By segmenting users into different groups (cohorts), teams can run sophisticated models that prove performance of campaigns or product UI changes. Teams should collaborate to articulate their hypotheses before running experiments and also rally around the results to generate insights.

Collaboration is the key

In a Harvard Business Review article, Robert J. Thomas of Accenture Institute for High Performance wrote, “What makes collaboration distinct, and so powerful, are the conditions that call it forth. Specifically, collaboration works best when people work together on problems that:

  • Don’t have an obvious solution: the problem addressed is not a routine one
  • Lack structure: there isn’t always a familiar process to follow
  • Require collective volition: some sort of sharing is needed but cannot be mandated”

That said, I’m sure you can see that product design is a ripe opportunity for collaboration.

Next time you tackle a project, I hope you’ll consider who else could be involved. Your results will be better for it.

原文鏈接

最后編輯于
?著作權歸作者所有,轉載或內容合作請聯系作者
  • 序言:七十年代末搓彻,一起剝皮案震驚了整個濱河市肝陪,隨后出現的幾起案子隶债,更是在濱河造成了極大的恐慌秆麸,老刑警劉巖,帶你破解...
    沈念sama閱讀 222,104評論 6 515
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件封锉,死亡現場離奇詭異痪寻,居然都是意外死亡闷旧,警方通過查閱死者的電腦和手機蓉冈,發(fā)現死者居然都...
    沈念sama閱讀 94,816評論 3 399
  • 文/潘曉璐 我一進店門城舞,熙熙樓的掌柜王于貴愁眉苦臉地迎上來轩触,“玉大人寞酿,你說我怎么就攤上這事⊥阎” “怎么了伐弹?”我有些...
    開封第一講書人閱讀 168,697評論 0 360
  • 文/不壞的土叔 我叫張陵,是天一觀的道長榨为。 經常有香客問我惨好,道長,這世上最難降的妖魔是什么随闺? 我笑而不...
    開封第一講書人閱讀 59,836評論 1 298
  • 正文 為了忘掉前任日川,我火速辦了婚禮,結果婚禮上矩乐,老公的妹妹穿的比我還像新娘龄句。我一直安慰自己,他們只是感情好散罕,可當我...
    茶點故事閱讀 68,851評論 6 397
  • 文/花漫 我一把揭開白布分歇。 她就那樣靜靜地躺著,像睡著了一般欧漱。 火紅的嫁衣襯著肌膚如雪职抡。 梳的紋絲不亂的頭發(fā)上,一...
    開封第一講書人閱讀 52,441評論 1 310
  • 那天误甚,我揣著相機與錄音缚甩,去河邊找鬼谱净。 笑死,一個胖子當著我的面吹牛擅威,可吹牛的內容都是我干的岳遥。 我是一名探鬼主播,決...
    沈念sama閱讀 40,992評論 3 421
  • 文/蒼蘭香墨 我猛地睜開眼裕寨,長吁一口氣:“原來是場噩夢啊……” “哼浩蓉!你這毒婦竟也來了?” 一聲冷哼從身側響起宾袜,我...
    開封第一講書人閱讀 39,899評論 0 276
  • 序言:老撾萬榮一對情侶失蹤捻艳,失蹤者是張志新(化名)和其女友劉穎,沒想到半個月后庆猫,有當地人在樹林里發(fā)現了一具尸體认轨,經...
    沈念sama閱讀 46,457評論 1 318
  • 正文 獨居荒郊野嶺守林人離奇死亡,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內容為張勛視角 年9月15日...
    茶點故事閱讀 38,529評論 3 341
  • 正文 我和宋清朗相戀三年月培,在試婚紗的時候發(fā)現自己被綠了嘁字。 大學時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片。...
    茶點故事閱讀 40,664評論 1 352
  • 序言:一個原本活蹦亂跳的男人離奇死亡杉畜,死狀恐怖纪蜒,靈堂內的尸體忽然破棺而出,到底是詐尸還是另有隱情此叠,我是刑警寧澤纯续,帶...
    沈念sama閱讀 36,346評論 5 350
  • 正文 年R本政府宣布,位于F島的核電站灭袁,受9級特大地震影響猬错,放射性物質發(fā)生泄漏。R本人自食惡果不足惜茸歧,卻給世界環(huán)境...
    茶點故事閱讀 42,025評論 3 334
  • 文/蒙蒙 一倦炒、第九天 我趴在偏房一處隱蔽的房頂上張望。 院中可真熱鬧软瞎,春花似錦逢唤、人聲如沸。這莊子的主人今日做“春日...
    開封第一講書人閱讀 32,511評論 0 24
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽。三九已至芙代,卻和暖如春吊奢,著一層夾襖步出監(jiān)牢的瞬間,已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 33,611評論 1 272
  • 我被黑心中介騙來泰國打工页滚, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留召边,地道東北人。 一個月前我還...
    沈念sama閱讀 49,081評論 3 377
  • 正文 我出身青樓裹驰,卻偏偏與公主長得像隧熙,于是被迫代替她去往敵國和親。 傳聞我的和親對象是個殘疾皇子幻林,可洞房花燭夜當晚...
    茶點故事閱讀 45,675評論 2 359