設計沖刺下載
by George Krasadakis
通過喬治·克拉薩達基斯(George Krasadakis)
Design Sprints can generate remarkable output for your company — such as a backlog of impactful ideas, functional prototypes, learning and key insights from customers along with real business opportunities.
Design Sprint可以為您的公司帶來非凡的輸出-諸如積壓有影響力的想法,功能原型,客戶的學習和關鍵見解以及真實的商機。
Consider this situation: your company needs to solve a major real-world problem — you need a novel solution, better than any other offering available in the market. You could be aiming for a product, a component, a system, a service or a process.
考慮這種情況 :您的公司需要解決一個重大的現實問題-您需要一種新穎的解決方案,比市場上提供的任何其他解決方案都要好。 您可能針對的是產品 , 組件 , 系統 , 服務或過程 。
In an ideal scenario, before making any investments, you would need the set of candidate solutions, prototyped and exposed to a controlled set of real users. This would enable enough signals and insights to make informed decisions and setup a better product development strategy.
在理想的情況下,進行任何投資之前,您將需要一組候選解決方案,這些解決方案應具有原型并暴露給一組受控的實際用戶 。 這將提供足夠的信號和見解,以做出明智的決策并制定更好的產品開發策略。
To get there — from a problem to functional prototypes enriched with customer feedback — you can follow standard paths. For example you can consult the experts in your organization, assign work-streams to different teams, coordinate the work, schedule brainstorming meetings, and wait in the queue to get UI designs and then to develop prototypes — a lengthy process with several drawbacks, dependencies, issues and risks.
為此,從問題到功能豐富的原型,再加上客戶反饋 ,您可以遵循標準的方法。 例如,您可以咨詢組織中的專家,將工作流分配給不同的團隊,協調工作,安排頭腦風暴會議,并在隊列中等待以獲取UI設計,然后開發原型,這是一個漫長的過程,存在多個缺點,依賴性,問題和風險。
Or, you can setup a powerful multidisciplinary team and ‘lock’ it in a room for a few days, with a clear goal: a shortlist of inexpensive, realistic prototypes of selected high-potential concepts, each enriched with feedback from real users.
或者,您可以組建一個強大的多學科團隊,并將其“鎖定”在房間中幾天 ,并有一個明確的目標: 從選定的高潛力概念的廉價,現實的原型入圍 ,每個原型都包含真實用戶的反饋。
A rapid innovation process outputting potential solutions to your problem and evidence from real users on how effective they are.
他們是 如何有效的快速創新的過程輸出到您的問題,并 從實際用戶的證據可能的解決方案。
This intense ideation and prototyping process comes in several forms and variations — a popular one being the ‘Design Sprint’, which promises ‘Solutions to big problems in just five days’. It uses ‘design thinking’ principles and introduces several techniques, tools and rules.
這種激烈的構思和原型設計過程有多種形式和變體-流行的是“ Design Sprint”,它承諾“在短短五天內就能解決重大問題”。 它使用“設計思維”原則,并介紹了幾種技術,工具和規則。
成功因素 (The success factors)
To get real value from a Design Sprint, you must emphasize on the right setup, preparation and readiness — or you may end up hosting an expensive multi-day brainstorming session outputting just noise.
為了從Design Sprint獲得真正的價值,您必須強調正確的設置 , 準備和準備工作 -否則您可能最終會主持一個昂貴的為期數天的頭腦風暴會議,僅輸出噪音 。
Having joined a large number of ‘ideation and prototyping’ sessions along with 10’s of formal ‘Design Sprints’, I would summarize the critical aspects and success factors in the following way.
在參加了大量的“想法和原型設計”會議以及十個正式的“設計沖刺”之后,我將通過以下方式總結關鍵方面和成功因素。
1.定義問題陳述 (1. Define the problem statement)
Don’t let the problem statement become your real problem! Most of the unsuccessful Design Sprints and prototyping sessions I have experienced so far, share this specific single point of failure: a poorly defined problem statement, which triggers time-consuming discussions, iterations and unnecessary regression — setting the entire process at risk.
不要讓問題陳述成為您真正的問題 ! 到目前為止,我經歷過的大多數失敗的設計Sprint和原型開發會議都共享這一特定的單點故障:定義不明確的問題陳述會觸發耗時的討論,迭代和不必要的回歸,從而使整個過程處于危險之中。
In contrast, the Design Sprints that started with clarity on the problem to be solved, moved on rapidly towards impressive solutions and prototypes.
相反,Design Sprint從明確要解決的問題開始,然后Swift發展為令人印象深刻的解決方案和原型。
The Design Sprints that started with clarity on the problem to be solved moved on rapidly towards impressive solutions and prototypes.
從明確要解決的問題開始的設計沖刺就Swift轉向了令人印象深刻的解決方案和原型。
Although the first day of the Design Sprint is usually about framing and re-framing the problem statement, I am convinced that having a good problem definition upfront is key for a successful outcome. You can always revise it and reset it as necessary during the first day, but a solid basis can make the difference. In any case, the team needs to be open to understand the problem and ready to consider different angles and unconventional approaches.
盡管“設計沖刺”的第一天通常是圍繞問題陳述的框架和重新框架,但我深信, 預先做好良好的問題定義是取得成功結果的關鍵。 您始終可以在第一天進行修改并根據需要將其重置,但是扎實的基礎可以有所作為。 無論如何,團隊需要開放以了解問題,并準備考慮不同的角度和非常規的方法。
There are several templates and methods to help you construct a valid problem statement — in general you need to describe the current situation vs the ideal state and the related implications for the involved users.
有幾種模板和方法可幫助您構造有效的問題 聲明 —通常,您需要描述當前狀況與理想狀態的關系以及對相關 用戶的影響 。
2.建立合適的團隊 (2. Set up the right team)
The synthesis of the team sets the foundation for the entire Design Sprint — you need diversity of thought, skills and perspectives along with expertise and creativeness — all combined in a small multidisciplinary team with the right culture: a team willing to share, collaborate, challenge assumptions, think big but also be pragmatic and purpose-driven.
團隊的綜合為整個設計沖刺奠定了基礎-您需要多樣化的思想, 技能和觀點以及專業知識和創造力 -所有這些都組合在一個具有正確文化的小型多學科團隊中:一個愿意共享 , 協作 , 挑戰的團隊假設, 大膽但也要務實和目標驅動。
A few factors can introduce serious risks to the process:
一些因素可能會給流程帶來嚴重的風險:
The wrong dynamics in the team (for instance, members do not express their ideas for fear of getting criticized by more senior members in the team)
團隊中的錯誤動態 (例如,成員不會表達自己的想法,因為擔心會遭到團隊中更多高級成員的批評)
a large team (add more than 6–7 people and you’ll get additional problems to solve)
一個龐大的團隊 (添加超過6–7個人,您將獲得其他要解決的問題)
or the wrong mindset (people tend to protect ideas versus sharing, or believe that they know the right solution, upfront).
或錯誤的思維方式 (人們傾向于保護思想而不是共享思想,或者認為他們預先知道正確的解決方案)。
The members of the team must ‘forget’ about seniority, hierarchy and authority. They need to be open to new ideas, new perspectives and different views. They also need to be ready to influence and get influenced, and to minimize the impact of bias and work together towards a shared mission — a great solution to a challenging problem.
團隊成員必須“忘記”年資 , 等級和權限。 他們需要對新思想 ,新觀點和不同觀點持開放態度。 他們還需要準備好影響和受到影響,并且 最大限度地減少偏見的影響,并共同努力實現共同的使命- 解決具有挑戰性的問題的絕佳解決方案 。
Physical space is also very important to allow the team to focus, express random thoughts and ideas, collaborate and quickly visualize concepts. You need a room with enough space, the right equipment and office supplies– such as writable walls, whiteboards and well, plenty of sticky notes.
物理空間對于使團隊專注,表達隨機想法和構想,進行協作并快速形象化概念也非常重要。 您需要一個有足夠空間的房間,合適的設備和辦公用品,例如可寫的墻壁,白板以及足夠的便簽。
3.確保團隊準備充分 (3. Make sure the team is well-prepared)
Design Sprints are demanding — fast and intense. The key to success is to have a well-prepared team. Even if your dream team consists of domain experts and senior business leaders, they all have to put some extra effort to get prepared — so they fully understand the problem and its wider context, the technology, the competition and the relevant global trends. Make sure that you clearly communicate to the team not only the context and the problem to be solved, but also the rules and the need to get prepared.
設計沖刺要求很高-快速而緊張 。 成功的關鍵是擁有一支訓練有素的團隊。 即使您的理想團隊由領域專家和高級業務主管組成,他們都必須付出額外的努力才能做好準備-因此他們完全了解問題及其更廣泛的背景,技術,競爭和相關的全球趨勢。 確保不僅與團隊清楚地交流要解決的環境和問題,而且還與規則和準備的需要進行清晰的溝通。
4.專注于構想 (4. Focus on ideation)
Assuming that a solid problem statement and the right preparation is there, the next most important element is ideation. While the Design Sprint process provides some tools to empower ideation, I would strongly recommend that you:
假設存在可靠的問題陳述并進行了正確的準備,那么下一個最重要的元素是構想 。 盡管Design Sprint流程提供了一些可增強構想的工具,但我強烈建議您:
increase the time allocated to idea generation, sketching and pitching and
增加分配給構思,素描和推銷的時間,以及
capture the ideas in digital format — with more detailed descriptions.
以更詳細的描述捕獲數字格式的想法 。
A backlog of ideas is a great asset — one of the most important outputs of the sprint and the key input to the prototyping phase. Ideas should not be left on sticky notes — even the non-selected ones could prove to be relevant and valuable in the future.
積壓的想法 是一項巨大的資產 ,它是sprint的最重要輸出之一,也是原型階段的關鍵輸入。 不應將想法留在便箋上,即使未選擇的想法將來也可能被證明是相關且有價值的。
This is why you need to feed the ideas generated in the Sprint into a centralized ideation system and make them discoverable by the right audience.
這就是為什么您需要將Sprint中生成的構想輸入到集中構想系統中 ,并使合適的受眾可以發現它們。
5.準備“快速原型制作” (5. Get ready for ‘rapid prototyping’)
Delivering realistic prototypes is a critical part of this process — since they will be used to capture user/ customer feedback. You don’t want your great concept to receive negative feedback due to a poor prototype implementation — that could mislead related decisions and undermine the overall value of the Design Sprint. Your team must be capable of real rapid prototyping — able to build realistic user experiences in just a couple of days or less.
提供逼真的原型是此過程的關鍵部分-因為它們將用于捕獲用戶/客戶的反饋。 您不希望您的偉大構想因原型實現不佳而收到負面反饋-這可能會誤導相關決策并破壞Design Sprint的整體價值。 您的團隊必須具備真正的 快速原型制作能力 -能夠在短短幾天或更短的時間內建立現實的用戶體驗。
Rapid Prototyping requires the right resources in the team along with a general technological readiness. For instance, to speed up the process you need to leverage any reusable software components you have, standardized datasets, artificial/ static data, UI elements, APIs, models and services. You will also need systems, tools and processes — for instance wireframing, software development environments and DevOps capabilities.
快速原型制作需要團隊中合適的資源以及一般的技術準備 。 例如,為了加快流程,您需要利用擁有的所有可重用軟件組件 , 標準化數據集 , 人工 / 靜態數據 , UI元素,API,模型和服務。 您還將需要系統,工具和流程,例如線框圖,軟件開發環境和DevOps功能。
Availability of special equipment might be important. For example, if physical prototyping is involved, a 3D printer might be of real value. Or if you expect Augmented Reality prototypes, you will need access to related devices — along with any templates, APIs and documentation.
特殊設備的可用性可能很重要。 例如,如果涉及物理原型制作,則3D打印機可能具有實際價值。 或者,如果您期望增強現實的原型,則需要訪問相關設備-以及任何模板,API和文檔。
6.尋找一位出色的促進者 (6. Find a great Facilitator)
This is a key role — in fact, I see the facilitator as the real protagonist of the Design Sprint. The facilitator must maintain the right pace, direction, energy levels and interaction patterns, to lead the team towards a clear, shared goal: define and prototype a great, novel concept solving the problem for real users.
這是關鍵角色-實際上,我認為協調人是Design Sprint的真正主角 。 主持人必須保持正確的步調 , 方向 , 精力水平和互動方式,以帶領團隊朝著清晰,共同的目標:定義和原型化一個偉大的新穎概念 ,為實際用戶解決問題。
It is a difficult profile to find — you need somebody mastering the process itself, but also having deep understanding of the problem and the particular business context. The facilitator must be capable of ‘reading’ the characters in the room and take necessary action to make sure that all voices are heard and considered.
這是一個很難找到的資料-您需要有人精通流程本身,但也需要對問題和特定的業務環境有深刻的了解。 主持人必須能夠“讀取”房間中的角色 并采取必要的行動 確保聽到并考慮所有聲音。
7.捕捉一切 (7. Capture everything)
Design Sprints are typically very ‘noisy’ with tons of sticky notes, ideas and stories on the walls — all these, in-between discussions, arguments, decisions and random thoughts. And yes, this ‘controlled chaos’ is exciting, but unless you have a dedicated person responsible for taking (digital) notes, you will end up frustrated, trying to decode colorful sticky notes and ‘reverse-engineer’ random drawings.
設計沖刺通常非常“嘈雜”,墻上有大量的便簽,想法和故事-所有這些都介于討論,論據,決定和隨意的想法之間。 是的,這種“受控混亂”是令人興奮的,但是除非您有負責記錄(數字)筆記的專職人員,否則您最終會感到沮喪,試圖對彩色粘滯便箋和“反向工程”隨機圖紙進行解碼。
To make the most of the thoughts and ideas, you need to capture them in a modern way — so they are discoverable and potentially usable.
要充分利用這些思想和觀念,您需要以現代化的方式來捕捉它們-這樣才能被發現并可能被使用。
8.尋找領導者,而不僅僅是“決定者” (8. Find a Leader, not just a ‘decider’)
I find the proposed decision-making process — with the super voting concept and the sticky votes on the sketches — oversimplified and very sensitive to team dynamics and the overall state of the team. Moreover, given the extra power, the decider must demonstrate deep understanding of the concepts, the ability to think strategically and communicate with clarity. You need a real leader there, not an ‘authority’ or ‘political’ person.
我發現擬議的決策過程-具有超級投票概念和草圖上的粘性投票-過于簡化,并且對團隊動力和團隊整體狀況非常敏感。 此外,考慮到額外的權力,決策者必須表現出對概念的深刻理解, 戰略 思考和清晰交流的能力。 您在那里需要一個真正的領導者,而不是“權威”或“政治”人。
The facilitator and the team should feel free to challenge whatever decisions made by the decider, by asking for justification — the business or technical reasoning.
主持人和團隊應隨時通過要求理由(業務或技術推理)來挑戰決策者做出的任何決定。
9.衡量成功 (9. Measure Success)
A design sprint is an expensive process — consider the associated direct and indirect costs of having x members full-time for z days. Thus, measuring the success of the Design Sprint itself is important. In the case of an ‘isolated’ sprint, success can be measured by processing direct feedback, outputs and mid-term outcomes — for example business opportunities and success stories linked with the deliverables of the Sprint.
設計沖刺是一個昂貴的過程 -考慮使z個成員全職工作z天的相關直接和間接成本。 因此,衡量Design Sprint本身的成功很重要。 在“孤立”沖刺的情況下,可以通過處理直接反饋,輸出和中期結果來衡量成功,例如與沖刺的交付物相關的商業機會和成功案例。
If you are running successive Design Sprints, you need a framework to capture and quantify Sprint outputs and impact — a flow towards a centralized ideas and knowledge repository. This data store should enable full tracking of the real business opportunities and financial gains associated with each of your Design Sprints — while specialized KPIs allow tracking the success of the overall innovation programme.
如果您連續運行“ 設計Sprint” ,則需要一個框架來捕獲和量化Sprint的輸出和影響-朝著集中式思想和知識庫的方向流動。 該數據存儲區應能夠全面跟蹤與每個設計Sprint相關的實際商機和財務收益,而專門的KPI則可以跟蹤整個創新計劃的成功。
The key question in this case is regarding the baseline to compare this ‘quantified innovation output’ against — to be covered in a forthcoming article.
在這種情況下,關鍵問題是關于將“量化的創新輸出”與之比較的基線,這將在即將發表的文章中進行介紹。
Design Sprints can generate remarkable output for your company — such as a backlog of impactful ideas (also with IP opportunities), functional prototypes, learnings and key insights from customers along with real business opportunities. At the same time, assuming proper and frequent execution, Design Sprints can lead to significant cultural improvements towards the ‘innovation mode’.
設計沖刺 可以為您的公司帶來非凡的輸出-例如積壓的有影響力的想法(也有IP機會),功能原型,客戶的學習和關鍵見解以及真實的商機。 同時,假設執行得當且頻繁,Design Sprint可以朝著“創新模式”帶來重大的文化改進 。
How to build Software Prototypes in rapid modeBest practices and guidance on how to rapidly build software prototypes and test your ideas to real usersmedium.com
如何以快速模式構建軟件原型 關于如何快速構建軟件原型并向真實用戶測試您的想法的最佳實踐和指南 medium.com
References
參考文獻
Problem statement — https://en.wikipedia.org/wiki/Problem_statement
問題陳述 — https://en.wikipedia.org/wiki/Problem_statement
Design Sprint book — http://www.gv.com/sprint/
設計沖刺書-http : //www.gv.com/sprint/
Design Thinking — https://en.wikipedia.org/wiki/Design_thinking
設計思維-https : //en.wikipedia.org/wiki/Design_thinking
- Photo by Will H McMahan on Unsplash Will H McMahan在Unsplash上??拍攝的照片
Related: How to lead innovation and drive change in engineering teams
相關: 如何領導創新并推動工程團隊的變革
Related articles
相關文章
Startups and the Importance of Agile Product Development
初創企業和敏捷產品開發的重要性
Rapid Prototyping practices for Software Engineering teams
軟件工程團隊的快速原型制作實踐
How to lead innovation and drive change in engineering teams
如何領導創新并推動工程團隊的變革
How (and Why) to Write Great User Stories
如何(以及為什么)撰寫出色的用戶故事
How to become a great Product Manager
如何成為一名出色的產品經理
Is this a prototype or an MVP? Well actually, it’s a proof of concept.
這是原型還是MVP? 實際上,這是概念的證明。
How to setup and lead a great product development team
如何建立并領導一支出色的產品開發團隊
Technology Innovation — Trends and Opportunities in 2018
技術創新— 2018年的趨勢和機遇
翻譯自: https://www.freecodecamp.org/news/how-to-run-a-successful-design-sprint-1702e0f79797/
設計沖刺下載