![]() The management team subsequently discusses the concept proposal. Make sure the team understands that the intent is to use it as a conversation starter, rather than the final recommendation to the client. In this case, you may want to present your draft proposal to the rest of the team. ![]() This is the straw man proposal that form the basis of the recommendation. To address falling revenues, the consulting team may recommend introducing additional sales offices. For example, it can be used to address falling revenues, uncover root causes to business problems & make recommendations for improvement. The straw man proposal can be effectively applied to different problems. This catalyzes the evolution of a mindset required to closely scrutinize the problem from all perspectives. It is about arguing & refuting the reasoning of any informal fallacies in logic. The team members should contribute to the overall discussions, critically asses other’s contributions & discard them if necessary. Therefore, all team members involved in this proposal should contribute to this process. From there, people can start to think more creatively, engage in fact-finding activities & conduct focused discussions. Using the straw man proposal, you can create temporary solutions. Often, the counter arguments lead to the ultimate solution. However, you should be ready to adjust & improve your hypothesis & assumptions based on new findings. Arguments & ideas that arise from the straw man proposal provide valuable feedback in a solution-oriented process. Instead, you should use it as a tool to arrive at the best possible solution. However, you should never expect this technique to provide the ultimate answer. The most common scenario where this technique most helps is when coming up with an initial hypothesis to arrive at a potentially overarching solution to a problem. You can also include customers in the brainstorming process. It is a great tool for brainstorming & creative problem-solving across all phases of an engagement & all levels of the organizational hierarchy. The straw man proposal is a way of discussing a problem with a group of people & developing a draft version. It is based on hypotheses & makes it easy to introduce increasingly better solutions in subsequent iterations. A straw man proposal is a concept version of something the team can discuss, break down, & improve. The straw man proposal concerns itself with the potential improvements, innovations or adjustments based on an original draft.Ĭompanies can leverage this technique to address problems & deficiencies with the intent to brainstorm solutions. Such straw men are easy to pull apart, destroy, & rebuild. Often used in a rhetorical sense, straw man refers to a human figure made of straw, such as a scarecrow. The straw man proposal was developed by McKinsey & is often used to solve customer problems in a more structured manner. Helps you get started versus getting bogged down seeking perfection.Involves other stakeholders in the building of the proposal.Helps brainstorm possible solutions when you have somewhere to start.Used to knock it down & develop better hypotheses.A problem-solving approach works well in a group setting.The premise is to create a draft version for criticism & testing, & then use the feedback for subsequent iterations, & eventually develop a proposal that is rock solid. As this approach is iterative & hypothesis-driven, the consulting team should be prepared to discard it if necessary & create a new straw man. ![]() It is an iterative process for arriving at increasingly better solutions. If you have decided to migrate to microservices then the next step is to design a target architecture.The straw man is hypothesis-driven problem-solving technique used by consulting powerhouses, such as McKinsey. My presentation Considering Migrating a Monolith to Microservices? A Dark Energy, Dark Matter Perspective describes how to decide whether to migrate to microservices. When this occurs, you should consider migrating to microservices. This typically happens when the application becomes large and complex and is developed by many teams.įor example, its deployment pipeline become a bottleneck. In many cases, once you have embraced the success triangle, your monolithic architecture is sufficiently loosely coupled, testable and deployable to enable rapid software delivery.īut sometimes an application can outgrow its monolithic architecture and become an obstacle to rapid, frequent and reliable software delivery. adopt DevOps, and reorganize into loosely coupled, small teams. It’s important to make the most of your monolithic architecture, e.g. Should you consider migrating to a microservice architecture? Let’s imagine that you responsible for a business critical business application that has a monolithic architecture and you are struggling to meet the needs of the business.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |