I teach a couple of consulting projects-type courses at Cornell. One is a Grand Challenges capstone-class for Dyson undergraduates in helping companies and organizations address one or more of the 17 UN Sustainable Development Goals. The other is a flagship-project class that is part the Masters in International Management program as part of the global CEMS Alliance, and it involves student collaborations and exchanges with 33 other top business schools and universities.
Each of these cohorts has different team compositions, problem statements, and situations to address for their client. Projects can involve diverse topics like addressing sustainability of the food supply chain and manufacturing capacity, promoting economic development and greater social equality in another continent, customer and market fit of a new product, workforce evolution given Gen Z, or marketing, branding, and product strategy for an international company.
Although projects are diverse and hard to find common bases of foundational knowledge, I have found it helpful to have bite-sized jump start material to help students get grounded. As part of the core, I have provided excerpts from my own book on bread and butter consulting concepts (for free), references to The So What Strategy for consultative communications, and a breathtaking short pocket reference to Scrum. These are all quite short books as evidenced by the spine thickness. People don’t have a lot of time to read given the heft and time pressures of projects.
Given that quite a few projects involve customer discovery, market fit, and/or diverse constituent interviews, I have decided to also add “Talking to Humans” as part of the reference books that I’ll draw from for these courses. It is a quick read book that can be completed in 1-2 hours. And it can be a great book to go back to for quick reference before doing any qualitative customer / product research.
This post is reproduced from an answer that I wrote on Quora to the question posed to me, “Is Behavioral Economics Actually Used in Business?”
Broad, conscious, and concerted efforts to apply behavioral economics probably did not begin until sometime after 2008 with the release of Thaler and Sunstein’s book, Nudge. And then when new applications of behavioral economics started, they seemed to be mostly applied in the government space. While many principles of behavioral economics have preceded that and have been applied, I think the introduction of a popular science book and clever packaging helped the principles rise to a new level of consciousness.
Since then, the implementation of behavioral economics/science initiatives in business has started to grow, but it’s still somewhat early. Back in 2010, I was part of a team that started one of the early behavioral finance centers with one of the investment manufacturing firms in the United States. We introduced thought leadership materials like some of the other firms, but we also took it further by equipping financial advisors with specific tools to help assess the behavioral architecture of retirement plans offered by companies.
One key observation I’ve had is that certain companies can have different strategies for implementing behavioral economics. This can include wanting to do holistic innovation that touches on service, products, and applications. Or they can pursue narrower approaches, like research and thought leadership. I wrote a book, Inside Nudging: Implementing Behavioral Science Initiatives in 2016, mostly to help bridge the gap between science and the application in business. That work is based on my background in closely collaborating with academics in behavioral economics and companies looking to be on the cutting edge.
Here are a few examples of how the field of behavioral economics has touched business in my corner of the world relative to behavioral finance:
As an additional reference, you might also be interested in checking out the book by one of my colleagues, The Smarter Screen. That book specifically addresses behavioral economics in a digital world.
Here are some thoughts on how consultants prepare for and handle these types of situations:
- Projections may be initially tested in safer settings. If projections end up being perceived as too wild or aggressive, it is better for this to happen in a working meeting or separate session before a “final” presentation is made. Following an iterative process and managing client expectations reduces risk for the consulting team.
- Projections are usually based on models with assumptions being made transparent. By making assumptions and modeling transparent, some focus can be taken off of the actual projections. The focus is more on the process and the assumptions, which of course lead to the projections. If the client disagrees with the assumptions or the process and modeling, problems can be resolved to minimize the possibility of clients “laughing” at the consulting team for the projections.
- Models and projections are often built by keeping the client team involved during the build process. This further minimizes risk of the client being surprised at the end. It also helps to increase ownership of the projections by the client. All projections have limitations of some sort. So let’s all own both the insights and limitations of the analysis.
- If the consulting team was not able to follow any of the processes above or if the consulting team could only feasibly do some of the elements above, then senior people on the team may need to handle a client that disbelieves the numbers and “laughs”. As example of how this could work, the partner could simply assert confidently that they believe the numbers and that a separate session could be set up to go through them. Another alternative might be for the partner to say that the consulting team will take a second look and perhaps one or more of the client members could be involved. Yet another option might be for the partner to suggest that some other scenarios and sensitivity analyses be performed. I will say though that consultants use their analytical training try to avoid being orders of magnitude off when putting forth projections. Or if they are going to provide projections that may be wildly off, they caveat that up-front.
All said, consultants try hard not to let situation #4 come up by actively working on items #1-#3 to reduce risk. It is important to remember that in consulting, the process is an essential part of the deliverable.
The post above was reproduced from a question that I originally answered on Quora.
Assuming that one has capable resources to get the job done, the most important thing needed for a competitive analysis is an articulation of the true problem statement. The need to perform a competitive analysis is not a problem statement in of itself. Is the problem statement a broad one to simply formulate strategy? Unlikely. Not focused enough. Perhaps it is about assessing the atrractiveness of services A, B, and C in a particular market? Or perhaps it is about a financial assessment of competitiveness from a risk management perspective? Or maybe the purpose is to determine the robustness of an organizational model relative to competitors? All of these? Some of these? Other?
The point is that competitive analysis is just a tool, and there are many tools. Which tool and approach one picks actually depends on refining the problem statement properly. Why do we want a competitive analysis? What problems are we actually trying to solve? Who in the organization is the analysis for? Get to the core needs. Then determine what competitive analysis approaches are the right ones given the problem, audience, time, effort, precision, and resources required.
Steve Shu specializes in incubating new initiatives with a primary focus on strategy, technology, and behavioral science. He is author of Inside Nudging: Implementing Behavioral Science Initiatives and The Consulting Apprenticeship: 40 Jump-Start Ideas for You and Your Business.
By way of background, I have long history in the consulting space and believe that effective communications separates leaders from the pack. And it’s something that one can continually work on to improve. Over the years I’ve read a number of books on communications such as books on writing, storyboards, logic, presentation construction, visual design, and verbal delivery. I’ve recently read “The So What Strategy,” a book on business communications, and wanted to share my thoughts on the book.
So what do I think about “The So What Strategy” by Davina Stanley and Gerard Castles (formerly communications specialists at McKinsey & Company)? “The So What Strategy” is an excellent book and provides readers with essential tools for more effective business communications related to writing, storyboards, logic, and presentation construction. Here are three reasons why it will be one of the top books for me to recommend to other consultants and business professionals:
- First, the book establishes a solid foundation from a structural point of view. The authors cover fundamentals from understanding one’s audience, the drivers for particular communications (e.g., context, triggers, and key question), bottom line messaging, and logical storyboards for key patterns that come up in business situations. The book also goes further to suggest concrete steps as to how one might incorporate storyboarding and other elements into both one’s own work and the internal processes of an organization.
- Second, the book is differentiated from other books, especially as it relates to addressing classic patterns one encounters in business. One classic book in consulting relative to communications is “The Pyramid Principle” by Barbara Minto (also ex-McKinsey). While Minto does a great job at explaining logical concepts that are pervasive in management consulting approaches such as mutually exclusive, collectively exhaustive (MECE) frameworks and tying these concepts to writing, Stanley and Castles dovetail with the same concepts and also cover seven classical storyline patterns that are suitable for business. These storyline patterns includes things such as communicating actions plans, suggesting recommendations, pitching ideas, providing updates, and several others.
- Finally, “The So What Strategy” comes in a modern package. While I feel the other two points I mention above are strengths, the book’s package is one of the biggest selling points for me. First, for the time-pressed professional, the book is a very rich but quick read. I got through the book in about two hours, which is surprising given how rich the book is in terms of content and substance. And yet the book can easily fit into the messenger bag of a road warrior consultant. Second, the book has concrete examples of emails, storyboards, and presentations; this helps readers actually see where communications can be improved and how following the authors’ frameworks can help. Third, the book provides concrete tools (such as checklists) and is well-structured for being a quick handbook.
I highly recommend “The So What Strategy”. Davina Stanley and Gerard Castles have done a remarkable job putting this book together. You can get a sample chapter on their website at http://www.sowhatstrategy.com. You can also take advantage of their online courses here.
I was recently asked on Quora, “Should one use heuristics at all as they are prone to cognitive biases?” What follows are my thoughts.
Heuristics usually allow people to make quicker decisions. For example, when catching a fly baseball, sometimes people use a gaze heuristic to keep the ball at roughly the same inbound angle by adjusting their position and moving forward or backward. This gaze heuristic allows us to quickly and dynamically make judgments to catch the ball as opposed to having to pull out the slide rulers, calculators, and physics books to figure out where the ball is going to land.
While heuristics can help with speed, sometimes we have the benefit of time to slow down to think about the consequences of potential biases and where the heuristics might lead us astray. For example, people often talk about a 4% drawdown rule/heuristic for using your wealth at retirement (e.g., use up 4% of your wealth each year). But one has to remember that using up your wealth is essentially an irreversible process. What type of risk analysis have you done? Have you assessed your longevity and potential variances both positive and negative? What happens if you live 40 more years? Have you accounted for negative health events? Have you thought about maximizing your happiness in retirement as opposed to economic numbers?
So heuristics can be used with some success. But heurisrics should be audited for their benefits and shortcomings, especially if the consequences of an error are significant enough.
I don’t claim this to be a good war story, but it is a war story has had a deep impression on me.
Early on in my career, I was asked by the managing partner on the project to help a struggling manager to help develop their plan for the business. When I got into the weeds, the problem was essentially an operations strategy and planning project. I brought a little rigor to the analysis, and I worked with the manager to break down scenarios and workflows and applying Little’s Law (i.e., average inventory equals average cycle time times average throughput) to validate the strategy, offer operational improvement suggestions, and calibrate the model. When the results were presented to the executives, they were pretty impressed. I was later privately told that I had helped to save the manager’s job. Take that for what it’s worth, but in any case, that made me feel really good. A key was that I helped to facilitate the strategy and analysis process, not completely do the work on my own.
Years later and in a totally different industry, I was asked to help with an operational assessment where the company had lost a tremendous amount of institutional business in the past year due to sales and operations processing issues. The executive team wanted me to take a look at the total business and dissect where things went wrong. There was some subtext that they believed that the one of the division managers had crashed the ship. Though it was never stated explicitly, I think the executives wanted me to find the implicating evidence. I ended up using similar techniques to the first project; first I tried to determine why people churned out as customers, and then once I attributed it to cycle times, I essentially used Little’s Law to determine why cycle times went up so drastically. In the end, what I found was that cycle time increases drove severe customer churn and that cycle time increases were not due to the manager in question. It was an issue caused by and owned at a broader level. I was done. Along with process recommendations, I presented the analysis results to the executive team. They were happy, but a bit surprised that I had not found implicating evidence for the manager. Once the project was complete, I was happy. I was happy that the client was happy, and I was happy with my approach and sticking to science as opposed to being swayed by biases or internal politics of the client company. Months later, I found out that the executive team ended up firing the manager. I’ve had mixed feelings ever since, ones that have never been fully resolved.
I ask questions like, do management consultants have impacts on people’s jobs? Or do management consultants feel that they are so important that they have impacts on people’s lives? Who owns the results? Is it the management team? Who owns the implications if people’s jobs are lost? What if jobs are gained? The answers to these questions are both debateable and situational. All said, to this day certain project types and situations trigger bad vibes for me, and I try to avoid them where possible.