Universal practices instill high performance
What makes some companies like Intel, Southwest, and Ritz-Carlton perennial performers? Is their secret charismatic leaders? Good timing? Grand vision? No. High performance isn’t about what organizations do, but how they do it. Customer Success teams can apply the same disciplines used by top-performing companies to dramatically increase results.
Jim Collins, author of Built to Last and Good to Great, says “dynasty” companies (those generating financial returns of at least 10x for 15 years or more) behave very differently than the rest. Unlike typical organizations, top performers are fanatically disciplined, empirically creative, and productively paranoid.1 Laser-focused and utterly relentless, they eliminate distractions and drive continuous improvement everywhere. Rather than follow industry experts or imitate others, top companies engineer their own breakthroughs using empirical evidence, observation and experimentation. And they remain hyper-vigilant, watching competitors intently and adjusting their strategies to thrive in a constantly shifting landscape.
High performing organizations like the ones Jim Collins describes depend on a set of interconnected, self-reinforcing management systems to instill their unique behaviors. Their management disciplines become embedded in the organization’s “operating system,” creating a culture of excellence in individual work areas and throughout the enterprise. The management systems they use are universally applicable, so Customer Success leaders can use them to realize similar benefits:
Sensory System
What it does: Methodically collects and interprets customer, market, competitive, regulatory, workforce, and technology trends to continually uncover new opportunities and threats.
Leading practices: Use quantitative and qualitative analysis extensively for market and product definition and performance monitoring. Implement internal and third-party “listening posts” in multiple channels. Increase relevance and salience by interpreting findings according to market segment. Systematically analyze, review and prioritize feedback for company business reviews, product roadmaps, and process improvements. Reduce “blind spots” by periodically challenging underlying assumptions and measurement techniques.
Application in Customer Success: Collect product usage, customer satisfaction, trouble ticket, and contact frequency statistics to generate health scores for specific customers and market segments. Utilize direct customer comments in CRM records and formal customer reviews for product and process deficiencies. Share discoveries via periodic, formal feedback sessions with development, sales, marketing, accounting, and operations leaders.
Planning and Review System
What it does: Inputs information, prioritizes actions, defines objectives, goals, strategies, tactics, and owners, and aligns financial and personnel resources to promote successful execution. Evaluates progress formally and periodically, holding people accountable, adjusting plans, and promoting learning.
Leading practices: Develop strategic (multi-year) plans that articulate long-term vision, objectives and goals, customer and market dynamics, competition, product and service roadmaps, value propositions, value delivery systems, staff development, risks, and financial pro-formas. Link strategic with annual plans and implement through product development and process improvement plans. Coordinate planning and review activities via calendars, and use scenario analysis to detect and quickly respond to environmental “triggers.” Involve all employees to build commitment for action.
Application in Customer Success: Participate in enterprise planning activities, share customer intelligence and help set functional objectives, goals, strategies and tactics. Prioritize, define, implement and track account management and marketing plans along with process improvement projects. Review progress monthly and quarterly.
People System
What it does: Defines jobs, employee knowledge and skill requirements, and facilitates screening, hiring, training, performance feedback, career development and overall organizational change.
Leading practices: Define short-term and long-term staffing and skills requirements as well as succession plans aligned with the strategic plan. Use structured screening, hiring, training, retention, and cultural indoctrination practices. Conduct both formal and informal performance reviews. Interpret quantitative job performance measures in proper statistical context. Collaborate to define and hold employees accountable for development plan execution.
Application in Customer Success: Craft position plans, metrics, knowledge and skill requirements, and development plans for CSMs to build stronger relationships, deliver onboarding, and uncover and advance sales opportunities. Characterize and use personality traits, in addition to education and past experience, to screen new hires. Give regular feedback, formally and informally, and avoid ranking.
Work System
What it does: Describes requirements and designs optimal workflows at a macro and micro level between customers, business partners, suppliers, company departments and work groups.
Leading practices: Map processes to identify critical handoffs, disconnects, metrics, and process improvement opportunities. Periodically redesign processes for enhanced speed, cost effectiveness and increased quality. Protect and develop core competencies to promote strategic advantages. Use partnership management and supply chain management techniques to influence change and improvement with third parties.
Application in Customer Success: Define the customer lifecycle linking onboarding, training, engagement, renewals, upselling and cross-selling activities using phone, e-mail, video, events, webinars, and social media contact as required. Define critical handoffs and feedback loops with sales, customer support, development, and accounting.
Metrics System
What it does: Focuses managers and teams on the critical few cause-and-effect relationships that keep processes under control and promote beneficial end results.
Leading practices: Deploy and manage daily operations across the enterprise via linked, balanced and aligned dashboards. List a critical few leading and lagging indicators in each dashboard to measure key business process performance, especially attributes driving competitive distinction and financial results. Calibrate dashboard signals using customer specifications or statistical process limits. Review periodically, take corrective action, and launch process improvement projects as signals dictate. Benchmark performance against competitors and “best in class” process references.
Application in Customer Success: Construct dashboards measuring outcomes (renewal rate, new revenue, etc.) and process factors leading to them (conformance to contact schedule, 30-day adoption %, etc.) as appropriate to the defined CSM role. Use a total of ten or fewer metrics, rolling up individual statistics into overall team performance. Set “red,” “yellow,” “green” action limits based on historical performance or goals articulated in the annual plan. Make dashboards visible in work areas, review and discuss performance with team members at least monthly.
Continuous Improvement System
What it does: Manages projects emphasizing customer focus, teamwork, and scientific methods to uncover root causes of problems, driving ongoing improvement in products, services and internal processes.
Leading practices: Execute cross-functional improvement projects using formal methods such as Lean Six Sigma, process simulations, and predictive analytics to maximize results. Choose projects based on financial or strategic impact, including major initiatives linked to annual and strategic plans. Increase effectiveness and customer value and reduce customer dissatisfaction, cycle times, and inefficiencies in all products and processes. In SaaS companies, diminish downstream bug detection, remediation, and customer churn costs through better upstream product definition, software development and validation processes.
Application in Customer Success: Implement formal methods to collect data and analyze processes to determine changes that increase customer retention and revenue and lower the Cost to Serve. Use statistical techniques such as logistic regression to study factors that impact customer churn, such as adoption rate, unresolved trouble tickets, or contact frequency. Design and execute experiments to test new ideas. Participate in company feedback loops to report software bugs and advocate for product and service enhancements.
Leadership System
What it does: Provides strategic direction, prioritizes actions, engages and inspires employees to perform at high levels, learn, and enact changes.
Leading practices: Articulate clearly and broadly communicate company mission, vision, values, goals and strategic plans. Engage the workforce and lead strategic change using formal processes. Model by example, recognize and reward high performance, and develop new leaders throughout the organization. Provide and receive performance feedback.
Application in Customer Success: Define the team’s purpose, goals and values. Understand and align with what motivates individual team members. Recognize and reward performance and hold people accountable. Incorporate leadership effectiveness feedback from superiors and employees in personal development plans.
When Customer Success leaders run their operations using the seven management systems above, their results rival the very best performers. Excellence becomes part of the culture, and customer churn, referrals and revenue relentlessly improve.
Excel-lens is a publication of Service Excellence Partners. We increase customer loyalty and business performance in the cloud computing industry. Contact us today.
Source:
1. J. Collins, M. T. Hansen, 2011. Great by Choice: Uncertainty, Chaos and Luck—Why Some Thrive Despite Them All.
You contact a company trying to get a problem solved and you find yourself passed between multiple departments. While people are sympathetic, their response is, “It’s not my job.” Despite multiple voice mails and e-mails, you get nowhere. Your issue has fallen into the company’s “white space,” the cracks between the boxes on the organization chart.
You’ve probably experienced white space issues inside your own organization, too. People perform departmental tasks smoothly, but there’s friction interacting with other groups. Processes don’t flow. Often things get “thrown over the wall,” there’s lots of finger-pointing, and it’s difficult to get things done.
Functional silo-ism first rears its ugly head when companies reach about 40 employees. At this threshold, companies must departmentalize to increase technical capabilities and bolster management’s span of control. But priorities slowly begin to shift. Soon pleasing the boss becomes more important than making customers happy. As the firm continues to grow, functional barriers get larger and more entrenched. Left unchecked, departmental relationships can become adversarial, paralyzing new product development, service delivery, customer acquisition, and customer care efforts.
Four tools that reduce silo-ism
Progressive companies deploy countermeasures to mitigate the effects of white space behavior. Top organizations combine the four management practices below to substantially diminish internal friction and dramatically increase performance.
1. Hoshin Kanri
What it is: Developed in the 1960’s at the Bridgestone Tire Company in Japan, hoshin kanri (literally translated “a bright, shiny needle”) is a rigorous, integrated system of planning, implementation, and review that points the way like a compass needle. Caterpillar, 3M, Toyota, Bosch and Danaher and many other leading companies use it.
How it works: Senior executives collaborate to prioritize common issues, and then decide on a single breakthrough. The objective is then decomposed into a smaller set of strategies, each featuring its own executive owner and performance measure. Leaders cascade the plan throughout the organization, finally defining implementation plans at lower levels. Formal hoshin reviews then roll up progress, allowing executives to eliminate barriers that crop up. The method’s closed-loop system promotes intense focus, relentless execution, and forward momentum.
Why it works: Unlike the common Management by Objectives (MBO) approach, hoshin aligns the organization around business, not functional, imperatives. Leaders pass these priorities down and reinforce them across the company. As a result, teams work towards enterprise-wide goals that transcend parochial concerns.
2. Process Mapping
What it is: A time-honored technique used to study workflows, process mapping reveals the “hidden factory” behind service work. Describing the process visually helps teams identify critical handoffs, gaps, rework loops, and queues. After pinpointing improvement areas, teams can then reduce errors, speed cycle times and reduce costs. Value Stream Mapping and Customer Journey Mapping are popular variations of the method.
How it works: Teams define process suppliers, inputs, outputs, customers, and requirements. Then they brainstorm tasks that must be completed to convert inputs into outputs, typically using Post-it® notes and butcher paper to record the workflow. Along the way, mapping participants identify improvement opportunities.
Why it works: Mapping allows people to see the systemic nature of business—everything is connected to everything else, and what happens in one area affects all others. People quickly realize that fast, efficient, customer-pleasing workflows trump choppy, disconnected vertical structures. Top organizations assign executives to lead cross-functional, key business processes, holding them accountable for optimizing teamwork across, rather than inside, department boundaries.
3. Enterprise Dashboards
What it is: The Japanese call an interlinked system of color-coded metrics nichijo kanri, or “daily control.” These displays help people at all levels manage the variables that lead to favorable business outcomes. Each manager’s dashboard typically monitors the key business process he or she oversees using 8-10 essential metrics that describe volume, time, cost, quality or other attributes.
How it works: Leaders define the critical few measures that really matter by analyzing company processes, economic models, and Value Propositions. They calibrate indicators by determining ranges of acceptable values based on stakeholder requirements, process capabilities and business goals. Managers then collect data act appropriately on the signal: “green” means everything is good, “yellow” means keep an eye on it, and “red” means take immediate action.
Why it works: With the right metrics, managers and teams focus on the most essential aspects of the job. They keep things under control and prevent downstream chaos. At top companies, executive dashboards reflect measures tied to cross-functional processes. When reward and recognition is tied to systemic improvement, managers and employees have greater incentives to work with other teams for mutual benefit.
4. Lean Six Sigma
What it is: Lean Six Sigma is the modern integration of two proven methods: lean production and six sigma quality. Lean (a technique pioneered by Toyota in the 1970s) emphasizes speed and helps identify and eliminate wasted time, motion, and raw materials. Six Sigma (a quality method named after an imperceptibly small error rate) aligns processes with customer needs and then reduces defects and excessive variation that causes dissatisfaction. Both have been used for years in manufacturing, and the combined approach is increasingly common in service environments.
How it works: Teams use formal methods to characterize process performance, estimate financial impact, uncover root causes of problems, design solutions, and implement changes. DMAIC (Define-Measure-Analyze-Improve-Control) or RIE (Rapid Improvement Events) provide teams with structure and statistical tools to effectively manage projects. Since teams make systemic improvements, results tend to be more dramatic and sustainable.
Why it works: Teams are often made of up representatives from all functions involved in the workflow. By working together towards common business goals, team members learn to appreciate the challenges people face in other functional areas. Besides creating more effective and efficient processes, a broader “systems view” and stronger interpersonal bonds between people promotes greater cooperation long after the project is complete.
White space problems are a natural part of organizational development. All companies deal with it in one way or another. Fortunately, proven tools and techniques can help young companies arrest its impact and promote scalable growth.
Planning is easy. Execution is hard. How can a monthly meeting keep an organization persistently on track to achieve its goals?
Nobody likes meetings, including me. People perceive them as time-wasters. Many have gone to “no PowerPoint” talks, got rid of chairs, or eliminated meetings entirely. In my view, these are extreme measures. Meetings serve a purpose. They provide important venues to communicate, learn, and make decisions. Yes, cut back on the number of meetings, but make the ones you keep more productive.
I think the best meeting agenda is called a Monthly Business Review (MBR). It’s a formal meeting (yes, preparation is required) designed to check progress on key plans, projects, and business performance. What makes it the best? Unlike other meetings, the MBR ensures the organization executes its business plan. The alternative, of course, is to do what most companies do: make a plan, and after a few weeks just go back to what people were doing before the planning session.
For an MBR, all functional heads and the CEO attend. A scribe and a timekeeper are assigned. Each manager has 15 minutes and may present only three slides. During the meeting, the scribe records issues and ideas that come up on a flip chart, and unless something requires immediate resolution, the topic is parked until the review is complete. The timekeeper also plays an important role. He or she prods managers to stay on topic lest the MBR lose focus and become interminably long. Here’s the agenda:
- Welcome and Opening Remarks (CEO, 5 minutes)
- Company-wide Dashboard Review (CEO, 10 minutes)
- Functional Round-Robin (15 minutes each VP):
- Dashboard Review
- Updates
- Successes
- Needs
- Hoshin Review (15 minutes for each strategy owner)
- Action Items (15 minutes)
- Other Items/Wrap-Up/Schedule Next Review (10 minutes)
The first essential element is the dashboard, consisting of the top ten metrics at the enterprise level and for each function. The company-wide dashboard may list things like revenue, expenses and customer satisfaction, whereas the marketing dashboard may include impressions, web visits, and lead conversion rate. Each measure is color-coded: green says everything is going well, yellow indicates things may be going off track, and red means take immediate action. Red signals get special attention; the manager describes the problem’s root causes and the actions being taken. Dashboards show cause-and-effect relationships, allowing managers to view the organization as a living system. The review also keeps managers focused on keeping the fundamentals under control. It provides context for decision making; if a new idea or initiative doesn't positively impact a key metric, it’s probably not that important.
The second essential element is the Hoshin Review. Hoshin kanri, a Japanese breakthrough improvement method, is an incredibly powerful tool for driving organizational alignment and change. During annual planning, the executive team collaboratively defines a mission-critical,
breakthrough objective, along with supporting strategies, owners, and performance targets.
An example hoshin objective may be, “Transform the sales process from a direct to a channel marketing and sales model” with goals to “increase annual revenue by 3x and reduce customer acquisition cost by 50%.” The objective is broken down into 3-5 major strategies and goals, such as “Recruit, contract, and implement third-party marketing relationships; goal of 3 by June 1.” Assigned strategy owners then form cross-functional teams and develop implementation plans. During the MBR, the Hoshin Review checks status, surfaces and removes any barriers to execution.
Order is important: business fundamentals before hoshins. Why? If the basics are out of control, working on more advanced initiatives makes no sense. Make sure the foundation is solid prior to reaching for the breakthrough.
Towards the end of the session, the scribe reviews any issues or ideas surfaced on the flip chart during the meeting, distilling them into action items, owners, and deadlines. Any outstanding action items from previous meetings not already addressed are also checked to make sure nothing falls through the cracks.
Obviously some meeting preparation is involved. Functional leaders meet with their teams in advance, rolling up data, interpreting signals, and planning actions for their dashboard metrics. Hoshin strategy leaders check progress on their project plans. The CEO must also prepare. He or she must review the top-level, enterprise-wide metrics and be ready to help executives prioritize next steps.
Work behind the scenes is also important. If the CEO notices chronic red signals or sluggish execution on hoshin strategies, he or she should meet separately with executives for 1-on-1 coaching sessions. Accountability for progress and results is important to maintain, but CEOs should avoid calling out individual struggles during the actual review.
So what do you think? If you had to arrange a meeting, wouldn't an MBR be one of the most valuable? If the goal is moving the organization forward, perhaps there’s no better agenda.
