It is that time of the year when you typically conduct planning session with your teams. I just came from one that I facilitated a week ago. I would like to share the planning methodology that we used. This planning process that I am going to share with you is nothing new and nothing that I came up with. You can find a lot of planning methodologies out there, if you Google it.
It is important to understand the current situation and needs that your organization has in a particular point in time, and then use it to tailor your planning process.
It is important that your team understands the entire planning process—what it is that you are trying to accomplish and what are the expected deliverables. I usually allot an adequate portion of the planning meeting to explain the “tailored” planning methodology. At this particular instance, I started out by showing the team the atlas of the universe; then the solar system; and then a picture of our planet earth; then I showed the a picture that represents our company or the business enterprise that we belong to; and finally, a box with an arrow going upward. I told the team, “that box represents us.” I explained why.
Mission and Vision
The box represents us—our mission and vision as an organization (see diagram below). Our mission defines our purpose— what is in and what is out. It represents, in the broadest sense, who we are. The vision is where we want to be as a group in a period of time in the future. The arrow from where we are now (point a) to where we want to be (point b) represent the shortest path to achieving our vision.
Our group had the opportunity to define our vision in our planning session last year, so that was something that we carried on and will carry on in the next couple more years. It is an input to this year’s planning process.
It is important to know where you are at the multi-year planning cycle to best tailor your team’s planning process for that particular year.
Last year, the first year of our planning cycle, we did the following:
- Invited key stakeholders of the company to speak to us about the business strategy, their expectations and needs.
- Gathered customer feedback from different forums and channels.
- Analyzed operative and project results from previous years.
- Conducted a team discussion around organizational concerns.
- Identified and discussed our Strengths, Weaknesses, Opportunities and Threats as a team.
- Established our vision for the next 4 years- articulated in a vision statement.
- Define our objectives and goals for the first year.
All the things that we accomplished in our planning session last year were used as inputs. We also analyzed the relevancy of some of our foundational objectives.
After reviewing the inputs from last year, the next thing that we did as a group was to do the “look back”. We talked about the operative and project successes from the past year. It was important to identify lessons learned and to convey key messages that align to the overall company direction and strategy. We had the team present those success stories by relating their experiences and journey.
Balance Scorecard and Strategy Mapping
To articulate our P&IT strategy we decided to use the time tested Balanced Scorecard approach and complemented it with Strategy Mapping. The Balance Scorecard, created by Robert Kaplan and David Norton, is one of the most popular and comprehensive tools for defining strategy and reporting performance in executing that strategy. This approach forces you to classify key measures and objectives used in your organization according to the four main perspectives— customer, financial, business process/ internal services, learning and growth. The key questions that we answered were:
- Financial – To succeed financially, how should we appear to our stakeholders?
- To achieve our vision, how should we appear to our customers?
- To satisfy our stakeholders and customers, at what services must we excel and what projects must we deliver?
- To achieve our vision how will we sustain our ability to change and improve?
The next complementary step is the mapping and analysis of the foundational objectives identified in the Balance Scorecard using Strategy Mapping techniques. By mapping how different objectives relate to one another, leaders can clearly see how to accomplish the stated objectives and how each one relates to the other. Many of those relationships go in a natural path from learning and growth to internal processes, to customer, finally to financial. To illustrate this concept, please refer to the diagram below. The blue boxes represent the identified foundational objectives classified in all four Balance Scorecard concepts. Then by relating those objectives based on causal linkage you form a story—your story, your strategy. In this strategy, the story goes:
You believe that by improving team culture, it is going to improve service delivery. And by improving service delivery, you believe that you will have more satisfied customers. And finally with improved service delivery and improved customer satisfaction you optimize IT cost. How those objectives flow and link represents your strategy.
After we defined and agreed on a strategy and with it the foundational objectives, the next step is the most tedious and difficult step of the entire planning process. It is the actual definition of departmental, team, and individual objectives. When you get to the point when you start identifying what you need to do to accomplish the strategy, real work begins. The team needs to have a clear understanding of the strategy, the role of their department/team and their individual role in making it happen.
- The first step is to break foundational objectives into departmental objectives. You can do this using a breakout session.
- Teams within their departments identified next level objectives and initiatives that they are responsible for.
- It is important to identify not only the initiatives/actions but also the measure and target by which the performance of the action will be measured.
In this process the common SMART method comes in handy. Your objectives have to be Specific, Measurable, Attainable, Relevant and Timely.
Finally, you have your mission and vision; you have your strategy and a detailed game plan (objectives) on how to bring your goals to fruition. The next challenge is to make it happen. I believe that the planning process does not stop after the initial planning process, which to me is the annual planning meeting. It is an ongoing process throughout the year. I like to borrow a term PMI uses- “progressive elaboration”. As you go through the year, you monitor and control the execution of the plan, as well as the changes to it. As you progress through the year, you will gain more information, priorities might change, and business requirements might change– you progressively elaborate your plan aligned to the business and IT strategy.
I attended a manager’s training program this week that my company organized. To be honest, I thought I would not encounter many new things, as I have participated in similar programs in the past already. I was wrong. One of the modules centered on leadership. I learned about improving leadership skills and effectiveness by focusing on specific leadership aspects. What resonated to me personally were the personal, relational and inspirational aspects of leadership that I often overlook. It helped that one of our program facilitators who shared about leadership, a seasoned HR director leader himself, gave personal stories from his own experiences that allowed me to see leadership through those aspects and ponder my own realization.
“I do not like that man. I must get to know him better.” – Abraham Lincoln
“Leadership is personal”, our facilitator passionately said and repeated. He took his statement to heart when he shared a lot of personal accounts about himself in the office and at home (about family) to demonstrate the personal dimension of leadership. I thought it was brilliant and the only way to bring the message across with effectiveness. What I learned is that— leadership is personal. It starts and ends with people following you because you are credible and you gained their trust. I have worked with the same boss since 2004, when I was assigned to participate in a business integration project in Europe. It is kind of strange how I call my boss and how he calls me—“my friend”. Because of working together for so long, you gained that level of trust and relationship. I see him as my personal leader and probably one of the reasons why I have been working in the same company for about 15 years now. Personal Leadership is about developing and projecting your leadership capability; being real; and demonstrating dedication. He embodies that. Personal leadership is the best way to gain credibility, loyalty and trust. As a leader you gain trust by demonstrating concern and understanding.
Ralational and Inspirational Leadership
“The greatest glory in living lies not in never falling, but in rising every time we fall.” – Nelson Mandela
“Leadership is like a contact sport”, our HR Director facilitator asserted in one of our discussions. He gave a lot of references to professional and collegiate sports, as to how coaches, as leaders, motivate and inspire their players and teams to achieve the best. I learned that leadership aspiration is not always about winning that championship trophy at the end of a tournament. It is about the inspiration and the motivation to have given the best effort possible—to leave every sweat and blood on the court. Our instructor showed us a 10 year old video, where NBA coach Mo Cheeks, then coach of the Portland Trailblazer, gave Natalie Gilbert a little help singing the national anthem. There is an American awareness for great performances of the National Anthem at sporting events. But for sheer inspirational impact, it’s hard to top what happened on April 27, 2003. This is a story of leadership, an example of humility, compassion and humanity. A tale of how one man, who decided in a few seconds, to help a girl sing the national anthem and inspiring millions by doing so.
What Mo Cheeks did expressed sentiments in the kind of message about leadership sports like basketball conveys. I think leadership has less to do with authority, punishment, rewards, and more to do with credibility, trust, empathy and love. If you think about it, if you have a professional career spanning 15 years or more (like me), the leaders who have motivated and inspired you, are the ones who made the most personal connection with you. There is vast untapped potential within organizations and communities to collectively perform at a level substantially greater when they have the right leadership. How can I consistently bring the best in my people? The answer is having an engaged team. How can you have an engaged team? Start with personal leadership.
More and more companies rely on innovation as a central factor to successful business outcomes and the only reason to invest in its future. In today’s slow growth market, tougher global competition and commoditization, pursuing innovations more often is the only way to keep customers happy and their competitors at bay. One type of innovation that has been very instrumental to many businesses is through the use of technology – let’s call it technology innovation.
Others might think that technology innovation means always having the latest and greatest systems available in the market, or having the fastest computers and networks. This is a myopic view of technology innovation. Most large companies have now implemented a digitized platform using well-established ERP software, like SAP and Oracle. Further developments of those ERP platforms are available to those who have them as foundation systems. If those companies are in the same industry, there is a big chance that they will pursue the same business processes and best practices in order to offer similar product and services to the same group of customers. How do companies then differentiate?
The reality is that, it is no longer true that simply having the right digitized platform is a determinant of sustained success. It is how you use technology to transform your business capabilities in a fast and agile manner that gives companies competitive advantage. Success on these technology innovation initiatives relies on a person who has both technology and business knowledge to navigate and orchestrate shaping and execution of innovative technology and business ideas. Those individuals that fuel the cycle of technology innovations in the enterprise now have a name – Business Relationship Managers (BRMs). Companies’ focus on innovation has given momentum to the growing emergence of the BRM role and discipline. According to BRMI, Business Relationship Management (what BRMs do) is about “stimulating, surfacing and shaping business demand for a provider’s products and services, ensuring that the potential business value from those products and services is captured, optimized and communicated.”
Peter Lijnse, an IT management consultant, wrote the following in his blog entitled BRM is about innovation.
“IT Service Management people are often good at stating, ‘We need to talk to the business.’ But very few understand the business they work for.”
This is so true. One essential competency of a BRM is business IQ and that’s assuming the BRM is already a technology expert. Many BRMs tend to come from a supply organization, and therefore, they have IT background, but it is not always the case.
Innovation is relevant only when it creates value to the customer, hence the importance of customer insights as input to the innovation process. Another common misconception about innovation is that it means new things – new platform, new functionally, etc. Not all the time. Innovation can be about new business value, not necessarily new things. Hence, it is the important for BRMs to understand the business to which they provide services. BRMs are key facilitators of technology innovation and they fuel faster innovation cycles and better business outcomes.
I am delighted to share this article I co-authored with Ibrahim Jackson about the Art of Business Relationship Management. This was published today in the Shared Services and Outsourcing Network Website.
Here is an excerpt of the article:
For many years, IT organizations responsible for deploying technology systems to enable enterprise processes have had one goal in mind – namely, to assure business-IT alignment. Today, however, as IT capabilities become more and more embedded in business capabilities, and given the pace of technological change and the pervasive nature of IT, alignment is no longer sufficient. The goal today, therefore, is “convergence”. This has given momentum to the growing emergence of the Business Relationship Management (BRM) role, which, according to the Business Relationship Management Institute (BRMI), is about “stimulating, surfacing and shaping business demand for a provider’s products and services, ensuring that the potential business value from those products and services is captured, optimized and communicated.”
Let’s examine Business Relationship Management from two perspectives: the functional and the organizational role. The BRM function provides the framework for how the IT organization interacts with peer business functions and departments. The BRM role is made up of an elite leader or group of technology managers that assume accountability for all technology solutions and services end-to-end – whether for a business area, brand, region, channel or division, depending on organizational design and technology capabilities. This role can be facilitated by an existing Chief Information Officer (CIO) in smaller, less complex organizations. For large enterprises, you may see multiple levels of BRM — BRM Lead, BRM Manager or BRM Analyst. Each role may vary in responsibility and all are accountable for the strategic alignment with the enterprise or organization.
BRMs, on a day-to-day basis, deal with technology, people and relationships. As such, Business Relationship Management is more an art than a science, expressing the “art” via application of knowledge, interpersonal skills and creativity. How a BRM best connects to his or her business partners varies, based on the BRM, their client, the business scenario, level of previous engagement and the rapport established with each relationship. Trust through confidence is the secret to success.
BRM Processes and Frameworks should be characterized by flexibility and a high variability of actions performed within the underlying processes. Within the BRM function, there is an inherent value to that variability. The nature of relationship management is fluid, dynamic, genuine and human.
Dr. Aleksandr Zhuk, Co-Founder of the BRM Institute, sums it up: “No one has ever defined a process framework that assures success in relationships. Think of marriage.”
You can read the full article by following this link: http://www.ssonetwork.com/business-partnering-customer-service/articles/the-art-of-business-relationship-management-shapin/
Business Relationship Management Frameworks – BRM Organizational Pyramid and BRM Process Groups and Competencies
I joined the professional group Business Relationship Management Institute in April this year. My friend, Vaughan Merlyn, is one of the Institute’s founders. Vaughan and I share a common interest. We are both active in the blogosphere and we write about IT, processes and technology management. Last month, within the BRMI collaboration space, I shared the BRM Process and Competencies Framework which I created. I got a note from Vaughan today that he will use it in his upcoming BRM Professional training. The framework has been a hit since I posted it in the BRMI collaboration space. I received notes that private and public organizations are already using it in their workshops. I am delighted about this and I would like to share this framework with all the readers of this blog as well.
Business Relationship Management Defined
Before I share the framework, let me first give you a background about Business Relationship Management as a role and competency. According to BRMI:
“Business Relationship Management is both an organizational role and a competency–one that can be held by business and service provider professionals whether or not they are assigned to a Business Relationship Management role. The concept of Business Relationship Management (BRM) is related to and employs the techniques and disciplines of Customer Relationship Management (CRM) that focuses on all aspects of interaction an organization has with its customer. However, while CRM most often refers to a company’s external customers, the BRM typically deals with a company’s internal customers or an internal provider’s products and/or services. The BRM is a crucial role that bridges a service provider and the business that depends upon that provider’s services. The most common BRM represents an Information Technology (IT) organization, but BRMs can also serve Human Resources, Finance, Legal, Facilities and other shared services functions.”
BRM Framework – Competencies and Processes
The BRM competencies published by the BRM Institute inspired me to work on a framework that lays out the processes that are important to the operative function of the BRM role. The purpose of this framework is to identify the processes performed by the BRM role while matching them with the needed competencies.
I started by identifying the processes that are performed by the BRM role in the organization. The process groups are: (1) Aligning (2) Consulting (3) Enabling (4) Servicing & (5) Evolving.
Next, I identified the sub-processes or activities in BRM that are associated with the core processes identified. I must say, since my background and experience has been in Information Technology, this framework is defined based on this field.
BRM Organizational Pyramid
I thought that the Process and Competencies Framework was effective in laying out processes that are important to the operative function of the BRM role but did not clarify the overall context of the role from the perspective of the business. It only focuses on conveying the actions performed by the role and the needed competencies. So, I came up with the organizational pyramid.
The BRM Organizational Pyramid is the overview of the BRM Process-Competencies Framework. This framework will help:
- To have a context diagram showing the foundational relationship of the BRM processes all the way to the business strategy. I chose the pyramid structure to convey the interconnectedness of the foundation activities with the over-arching business objective.
- To highlight other support elements that help enable the BRM function. The previous framework mapped the processes with the competencies. I reckon that there are other support elements that are equally essential for the BRM in the performance of its role, such as: organization, knowledge base, methodologies, and tools/ systems.
- To show the hierarchical relationship from top (strategy) to bottom (processes). Before you perform the BRM role you start with strategic partnership, by aligning the role with the business strategy. The next level shows the structure of the partnership in a form of a business service partnership agreement and corresponding key performance indicators.
The aim of the pyramid is to clearly show the relationship of the five process groups to the Business Value Alignment (strategy), and then to the Business Service Partnership (structure) that defines the manner in which BRM is expected to be performed within set performance parameters. The support layer represents the enablers of the role– much of these are what the BRM Institute provide to its members.
I hope you find both these frameworks useful in creating, developing and improving a BRM function in your organization. If you wish to access more materials and collaborate with other BRMs, the BRM Institute is the right professional group for you.
In innovation, you aim to introduce something new; make changes in anything established. You could go right or could go wrong. Of course you do all preparations necessary to go right every time, but if you don’t, you take the lessons learned and be better next time.
Romeo Siquijor is a good friend and compatriot. He now heads Information Security in CEMEX in Mexico while I found my way to Houston after several stints in different countries. We both started as young IT managers in the Philippines. Our offices were adjacent. The thing I remember most was Romeo repeatedly telling his IT Operations team that “failure is not an option” — like it was their mantra. I did not disagree with him, but it was not the same message I would tell my team.
I headed the IT Business Processes group at that time. My department’s task was to enable and support IT solutions. For us, the mandate was to find new ways to do things, to innovate, and to test new tools with potential application to our business processes. Of course, I wanted my team to succeed but on the other hand, I did not want to have the fear of failure limit their quest for new things. I believe that sometimes the cost of finding innovation is failure – finding out what does not work on your way to finding out what does.
While working with our commercial department, we implemented a sales automation tool using handheld devices. Unfortunately, it did not fly when we piloted the project and we failed. We did not get the buy in because the tool was not user-friendly and robust. The sales managers simply did not use it. We explored another innovation we called mobile selling. Romeo helped design a simple technical architecture to run it. At the time, in 2003, text messaging or SMS was already big in the Philippines. It was a phenomenon and the use of it quickly became part of our culture. Our goal was to incorporate the use of texting to our sales process. We developed a tool that would allow our customers to request orders using SMS and they did just that. In just a few months, 60% of our sales orders were coming from our mobile channel. We were open to exploiting the best technology at that time by applying it to our sales process but we were not sure how our customers will react. We were willing to fail and so we took a risk and gave it our best shot.
When mobile selling was already operating, it became a mission critical application. The system was hosted by the IT infrastructure that my friend Romeo manages. In that perspective, I loved it when he told folks “failure is not an option.” I did not want any service interruptions to impact my mission critical applications. Romeo values productivity, availability and reliability. He wanted no failure and no surprises. He wanted things done yesterday, done better, faster and cheaper today.
My goal is to show you two different perspectives from two different functions in IT. “Failure is not an option” is a good mindset for day-to-day IT service delivery. Although, I would argue that this does not apply to areas whose mandate is to innovate. In innovation, you aim to introduce something new; make changes in anything established. You could go right or could go wrong. Of course you do all preparations necessary to go right every time, but if you don’t, you take the lessons learned and be better next time.