Skip to main content

Tag: Communication

It’s Time to View Your Role as a Communication Expert

kupe Oct29I teach a class on applying improvisation skills that focuses on how to be a better team player, collaborator and communicator. I start the class off by asking people what skills they need to be effective in their role. In this session people generally say communication skills, problem solving, negotiation skills, influence, teamwork, etc. Many of the underlying competencies in the BABOK. They also bring up the multitude of techniques familiar in our community like use cases, user stories, impact mapping, context diagrams, workflow diagrams, etc. In my last blog post I argued that decision making was not an underlying competency it was what a business analysis professional does. In my classes and here in this post I argue that the same applies for communication skills.

As I was formulating my thoughts for this post I attended a Greater Atlanta IIBA chapter meeting where a panel discussed communicating to executive level employees. My friend and BA thought leader Jonathan Babcock made a statement that resonated with me. He said, in so many words, BA’s need to be great communication experts. I was so moved I almost gave him a standing ovation.

You need to view your role as communication expert. Your goal is not to complete a template, your goal is not to document Use Cases, your goal is not to help groom a backlog. You goal is to have the necessary stakeholders involved in your initiative gain a shared understanding of the problem and how to go about solving that problem. It’s that simple. The tools and techniques are there to help you communicate. They are not what you do.
Other professions, not yours, have communication as an underlying competency. For example, a plumber. Their main competency is plumbing services. Their goal is to get water from point A to point B without any leaks (over simplified, but you understand where I am going). Their main role is not communication. Yes, they have to communicate with other team members and a homeowner, but it is truly a secondary competency.

Communication challenges are at the core of why in our profession best practices are not always the best practice. Being a communication expert means you are communicating with individuals. Every individual is different. Everyone has their preferred communication style, their own information needs. So when someone says I have a requirements best practice you can’t assume it will work for you and your team. That practice was the best for their team. You need to understand what works for your team and your situation. Now don’t stop learning from others. Just use other people’s experiences to help come up with your approach.

In our community waterfall vs agile is a big topic. This comparison and these conversations are masking the real issue. If you have the mindset of communication first, nothing else matters. Regardless of methodology used you add value to your team by helping gain that shared understanding. Do what is necessary to gain that. New techniques or new uses for existing techniques surface all the time. Use them to help you communicate.
When you view your role as a communication expert you will start to see how to identify when you have done enough analysis. Knowing when you have done just enough analysis is not when a technique is complete to a certain level of quality. You know it when you have communicated clearly and there is a shared understanding. When that goal is reached you are done. There is no silver bullet here. If everyone on the team is very familiar with the business area and problem to be solved it may happen faster. If the problem and solution are complex and there are new team members it will take longer.

Without being able to see your faces or ask you directly I am going to assume we all have a shared understanding. If not, let’s continue the conversation in comments below.

All the best,
Kupe

Don’t forget to leave your comments below.

The BA Practice Lead Handbook 12 – Communicating Strategically: It’s like Stakeholder Management on Steroids

Use strategic communications as your most effective tool to ensure you realize the full value of your BA Practice, and your organization knows it. Since project sponsors seldom measure accurately and then communicate the value derived from project and program solutions, the BA Practice Lead ensures these data are captured and shouted far and wide. An effective BA Practice focuses primarily on business value, the true measure of project management and business analysis effectiveness.

Strategic Communication

For the BA Practice Lead to be taken seriously and looked upon as a credible leader of change, she must engage in strategic communications. This involves:

  • Thinking strategically, holistically, systematically
  • Crafting powerful messages that are impactful and memorable
  • Influencing positive decision making through intentional and targeted strategic communicationkitty Oct21

Strategic Thinking

To elevate your messages to make sure they are heard, begin to think differently about projects:

  • Projects are essential to the growth and survival of organizations
  • Through projects we innovate and adapt to changes in the environment, the competition, and even the marketplace
  • Projects and project teams are our most effective tools used to execute strategy and therefore, to create value
  • Holistic, systems thinking transforms our vision of project teams from tactical implementers to strategic executers of change
  • Instill in your BA team the power of strategic thinking

It is critical for the BA Practice Lead to think and communicate holistically. In the context of business, holistic thinking takes into account the purpose, values, function, process, and structure of the organization. Holistic thinking forms the basis for everything BA Practice Leads do:

  • Examining a complex system
  • Developing the business design structure, the business model
  • Problem solving
  • Forming and executing strategy
  • Communicating strategically

Holistic/systems thinking is the process of understanding how systems influence one another within a whole. In nature it applies to how ecosystems such as air, water, movement, plants, and animals work together to survive or perish. In the context of business solutions, it is the study of elements and their relationships with each other and with other systems, rather than in isolation. In organizations, systems consist of people, structures, data, processes, and technology that work together to make an organization functional or dysfunctional. The only way to determine why a problem or opportunity exists is to examine all elements within the system.

While analytical thinking involves understanding a system by thinking about its parts and how they work together to produce larger-scale effects, holistic thinking involves understanding a system by sensing its large-scale patterns and reacting to them. BAs need to understand the difference between the two types of thinking, and when to employ each.

  • Holistic, systems thinkers get a general feeling about a situation to open their minds to subtle nuances of complex situations. They are often parallel processors, examining widespread simultaneous activity instead of a controlled, step by step process. They are often creative and intuitive, therefore focusing on the big picture and innovation.
  • Whereas analytical thinkers understand how the components of the system function and work together. They usually possess good memories and pay close attention to the inner details of a situation.

The BA Practice Lead understands that her BA team is leading projects that are making changes to a set of parts connected by a web of relationships. Through these projects, her team is instrumental in executing strategy through multiple, interrelated projects. This is the story that needs to be told through strategic communications coming from BAs, and especially from the BA Practice Lead, for they are constantly participating in:

  • Strategy Formation through enterprise analysis, competitive analysis and creative, intuitive thinking
  • Strategy Decomposition to goals and objectives captured in the business case
  • Strategy Execution through programs and projects
  • Strategy Correction/Refinement as more is learned and the environment changes
  • Strategy Measurement of progress along the journey
  • Strategy Communication to describe the progress and demonstrate business benefits realized through projects.

Assess the Political Landscape

The first step in crafting your strategic communication plan is to assess the political landscape. Your organization is dynamic, adapting to changes all around. So, this assessment must be done often.
Understanding organizational politics facilitates strategic thinking. Make no mistake, organizational politics influence the success of your BA Practice and of the projects your BAs are leading. Organizational politics is comprised of the internal structures of your organization and how it deals with power and influence. Politics is neither good nor bad, it just is. Things happen when politics works:

  • Decisions are made
  • Projects move forward
  • Deals are cut
  • Goals are met

How can that be bad?

Positive politics gets positive results for the team, for the organization, and ultimately for you as BA Practice Lead. As a positive politician use your influence rather than authority or manipulation to achieve goals. Ensure you are operating from a positive position, a solid basis from which to influence, which includes:

  • Status – your role as BA Practice Lead needs to be positioned high enough in your organization to command respect.
  • Trust – your colleagues, whether on a peer level, above or below you on the organization chart must trust you. Trust is earned slowly through positive interactions.
  • Integrity – never sacrifice your integrity. Never.
  • Consistency – maintain a ‘steady as she goes’ posture. Carefully craft your communications so that they tell a story and are consistently positive and strategic oriented.
  • Knowledge – become a quick study. Know what you are talking about, and know when to dive into the details and when to stay at the executive level. Know your audience, and what type of communication is appropriate to them.

To assess the political landscape, gather business intelligence about your customers, stakeholders, the environment, your status, the status of your BA team, and any landmines and risks. This is sort of like a stakeholder management approach on steroids.

Customer and Stakeholder Intelligence

Identify your customers and stakeholders that:

  • Provide budget to your project
  • Provide oversight
  • Provide requirements
  • Provide input
  • Get output
  • Depend on your deliverables
  • Benefit from your project’s success
  • Suffer from its success

Determine the level on involvement and importance. For each key customer/stakeholder, capture elements of business intelligence information:

  • Role
  • Awareness
  • Opinion
  • Importance
  • Current level of support
  • Level of support needed

Capture the information in a simple tabular format similar to the one below. Note: customize this and the other templates presented in the section to meet the unique needs of your organization.

kitty Oct21 1

Legend:

kitty Oct21 2

Influence Strategies

Then, identify the issues and concerns regarding the BA Practice that are important to each stakeholder. Ask: What’s in it for them? What do they need to view the BA Practice positively and actively support it? What actions will you take? Develop an influence strategy for each key stakeholder

kitty Oct21 3

The Political Environment

Work with your BA Practice Steering Committee to determine:

  • Is the business case for your BA Practice solid? Can we demonstrate measurable results?
  • Is the BA Practice politically sensitive?
  • Are there major political implications?
  • Is there impact to the core mission?
  • Do you have a strong executive sponsor?
  • What are the unspoken expectations?
  • What is the decision-making process?
  • What are the cultural norms?
  • Is the communication and coordination effort challenging?

Capture the information in a simple tabular template.

kitty Oct21 4

Your Political Management Capabilities

Armed with this information about the political and cultural environment, work with your BA Practice Steering Committee to assess the political capabilities of your leadership, including how well you do the following:

  • Enlisting the help of an executive sponsor
  • Organizing and chairing your BA Practice steering committee
  • Making yourself and your BAs experts about the business
  • Promoting yourselves and your BA Practice
  • Managing BA Practice benefits (ROI)
  • Managing virtual alliances
  • Facilitating, negotiating, and building consensus
  • Managing conflict
  • Developing a political management strategy for your BA Practice

Capture the information in a simple tabular template.

kitty Oct21 5

The Landmines and Risks

Using the information you have collected, assess the political risks to the sustainability of the BA Practice. Determine strategies to lessen the impact of the risks that may negatively influence the BA Practice, and leverage those that are positive. Work with your steering committee to devise strategies to:

  • Gain high-level support
  • Build alliances and coalitions
  • Control critical resources (money, people, information, expertise)
  • Control the decision process
  • Control the steering committee process

Capture your political management strategies in a simple table similar to the one below.
kitty Oct21 6

Political Management Plan

For each strategy, identify what success looks like. Focus on outcomes, how you will evaluate the effectiveness of the plan. Continually refine your strategy. Capture your success strategies in a simple tabular template.
kitty Oct21 7

Craft Strategic Messages

Armed with the “business intelligence” you have captured, and your political management plan, you are now ready to begin to craft customized messages to your key stakeholders and customers.

Really Getting Heard

When presenting information to overworked executives, managers, employees, and distracted customers, you only have a few short minutes to get your message across. You need to become expert in: constructing memorable messages, customizing your message for the audience, really getting your message heard, and getting the decisions you want quickly so that forward progress is not stalled.

The Message

Compose a customized message for each key stakeholder. First, determine the purpose of the message. Is it simply to create awareness about your BA Practice objectives? Is it to enlist support for your BA Practice? Is it to dispel negative feelings about your BA Practice? Is it to make a decision about your BA Practice approach? Is it to gain support to resolve an issue?
Once the core purpose of the communication is understood, draft the message, composing it from the stakeholder’s perspective. Be sure to determine “What’s in it for them?” and tailor the message accordingly.

The Catch Phrase

“A minimum of sound to a maximum of sense.”
Mark Twain

Catch phrases adroitly capture the heart of your message. In the media world, catch phrases are referred to as sound bites, a very short piece of the message. It is a short phrase or sentence that deftly captures the essence of what you are trying to say. The goal is for the catch phrase to stand out in the audience’s memory; to be memorable; to clearly and cleverly make the point; to capture the heart of the message in a snippet. Examples of catch phrases include: “I have a Dream” “The Buck Stops Here” and “Joe the Plumber”.

The Slogan

A slogan is an effective technique that is used in advertising. It is also designed to make the message memorable. A slogan is a short phrase used as a rallying cry. It is intended to be motivational – to be a call to action. Examples of slogans include: “Don’t Leave Home Without It” “Yes We Can” “Just Do It” and “We’re the Dot in .com”.

The Pitch

You are now ready to develop your pitch, your “elevator speech” that takes no longer to deliver than thirty seconds and is about 100-150 words in length. Use a compelling “hook” that motivates people to further engage by including catch phrases and slogans. Capture your pitch in a simple tabular template.

kitty Oct21 8

Steer Your Steering Committee

Many BA Practice implementations are challenged – or even fail – because the project leadership team does not perform the critical analysis that is needed to determine the best path forward, at the start of the project and all along the way as more is learned and issues arise. The BA Practice Lead does not take the time to stop, analyze all possible solutions to business problems, or assess varying approaches before marching ahead. Once we are clear about the business problem or opportunity the BA Practice is going to solve, should we resource the practice in house? Do we have the appropriately skilled and talented BAs? Are they available? Do we need outside expertise? How fast do we need the practice to be fully functional? What are our competitors doing? The list goes on and on.

Getting the Decision You Want

When proposing a new initiative, escalating issues, proposing a course correction, securing the best resources for your practice, advocating to accept scope changes that add business value, you are essentially in a sales role, seeking approval from upper management. There are many pitfalls: management is impatient; we must not only be brief, we must also demonstrate the wisdom of the recommendation we are making. To do so, the wise BA Practice Lead works with an expert team to identify all potential options – fostering creativity and “out of the building” thinking. Then, you are ready to ask for a decision for your recommended option.

So, how can you make sure you get the decision you want? You need to facilitate BA team, augmenting it with additional SMEs who are influential, to analyze the issue, identify all potential options, and propose the most feasible solution. Use the results of your alternative analysis as decision-support information when presenting your recommended approach. Include the names of those who participated in the analysis, all the options considered, and the feasibility of each option: the economic feasibility, the time-to-market feasibility, the cultural feasibility, the technical feasibility, the success feasibility, the business process feasibility, the feasibility of achieving an innovative solution. After this analysis is complete, it is usually very clear which option is the most feasible. Capture your feasibility analysis in a simple Alternative Analysis Worksheet, and use it as decision support information when meeting with your BA Practice sponsor and steering committee.



kitty Oct21 9

Putting it all Together

So what does this mean for the Business Analyst?

Don’t let the political environment steer your project in the wrong direction. Establish Political Management and Strategic Communication Plans to negotiate environmental land mines, manage stakeholders’ influence, develop your political skills, respond to political risks, and seek approval for recommendations that are supported by rigorous alternative and feasibility analysis. Your team will respect you, and your management team will notice your logical and disciplined approach.

So what does this mean for the BA Practice Lead?

Model the process to create and execute Political Management and Strategic Communication Plans for your BA Practice implementation and sustainability approach. Require your BAs to employ some or all of these techniques as they negotiated the political landscape.

To communicate effectively, the BA Practice Lead prepares unique communication strategies for the major stakeholders of the BA Practice. Your goal is to explain the value of Business Analysis, driving an understanding of the WIIFM (What’s in it for me?) for all key stakeholders. Effective communications involves an enterprise focus, an emphasis on executing strategy and advancing enterprise capabilities, delivering innovative products and services, and measuring and communicating improved project outcomes.

Strategic communication requires targeted approaches for each key stakeholder. First, identify WIIFM for each key individual and group (refer back to article 2 for ideas).

  • What’s in it for the CIO? The CFO? The CEO?
  • What’s in it for the Business Manager?
  • What’s in it for the Technologists?
  • What’s in it for the Project Manager?
  • What’s in it for your customers?

Then, devise a customized communicate strategy and key messages for each stakeholder. Convert the messages to a short, concise ‘elevator speech’. Determine the appropriate media and timing of the communication. Focus communications on how projects using mature BA practices produce value to the customer and wealth to the bottom line. After each communiqué, determine the effectiveness of the message, and make improvements to it for the next time.

Some content is adapted with permission from The Enterprise Business Analyst: Developing Creative Solutions to Complex Business Problems by Kathleen B. Hass, PMP. © 2011 by Management Concepts, Inc. All rights reserved. The Enterprise Business Analyst: Developing Creative Solutions to Complex Business Problems

Don’t forget to leave your comments before.

Can’t Answer Key Questions? Sit Back, Reflect, then Plan Wisely.

Sometimes Business Analysts find themselves on a project where it is not quite clear what is expected from them, apart from delivering right first time and on time: “BA stuff, you know…”

This article aims to identify some signs that hint that there is a lack of “whys” being answered, and which are required for you to effectively deliver “BA stuff” and list some options you can take to mitigate the related risks.

Missing Why #1 – Why this project? 

Many of us will have experienced projects that are missing:

  • a link to strategy
  • a clear set of objectives
  • a crisp rationale that supports the “why” the project exists.

Project team tend to overlook this, after all, the general consensus is that there must be good reason for this project otherwise we wouldn’t be working on it, would we?

Yet, if any of the points above are missing, then it is hard to conceive a set of artefacts that enable a traceable transition from any high level “statement” (e.g. business needs) down to a lower level of detail (e.g. test cases). Not knowing exactly what we are aiming to solve, often leads us to misguided decisions about what needs to be done, and the inevitable trail of objectionable side effects (e.g. waste of time, money and enthusiasm to name a few).

Verbal or written clues to look for:

  • “We have everything in place so let’s start building – we can address the details later.”
  • “We need more doers than thinkers. Let’s skip all that academic exercise and start delivering real work.”
  • Isn’t it that obvious?!
  • “Problem statement? This project doesn’t have a problem, everything is under control!”

Missing Why #2 – Why this approach?

This does not need to be preceded by #1, as sometimes when a project starts, it is “mandated” to adapt current “best practices”. Often pragmatism is quoted in those circumstances to avoid tasks, deemed to be superfluous, being undertaken by the project. Your experience tells you that you know a way that would work better in these circumstances, so you are left wondering “why” this approach was chosen.

Verbal or written clues to look for:

  • “We cannot miss the gate date we’re scheduled for…”
  • “Agile means we get this done faster”.
  • “We can capture it all in the use cases”.
  • “This plan is too lightweight”.
  • “Don’t worry, the builders know exactly what to do with that”.
  • “Our delivery method is pretty generic, so we only use what we need”.
  • “This is paralysis by analysis, we don’t have to overcook it”.

Consider “acting” out of the box, not just “thinking” outside of it.

Understanding “why this project?” is paramount, and the rationale should be cemented in the business case, sprint zero, or similar funding stage. These pre-project phases can be stressful due to multiple negotiations, studies, plans, meetings and the final agreement on project sponsorship. 

Often there is a “agree to agree” take on issues that are difficult to reach consensus on. It is not uncommon that key stakeholders assume arbitrary commitments to keep the ball rolling. This usually results in high levels of anxiety with the pressure to release a tangible project outcome as soon as possible.

In this critical moment, it is vital that the Business Analyst or their team take a deep breath and assess what is on the table, what is missing, and start drafting the business analysis plan.

Some possible steps:

  1. Verify whether the available information is sufficient to allow a robust and consistent business analysis plan. If not, then the gaps and uncertainties should be mapped and addressed in a “project initiation plan”.
  2. Produce a clear set of problem, or opportunity statements, affected parties and desired outcomes.
  3. Disclose a tactical plan, along with some options, that address the issues previously exposed.
  4. Provide a review that clearly shows how any estimate could be impacted by the lack of capital information and how the “project initiation plan” can mitigate these risks and even leverage the expected outcomes of the project.
  5. Demonstrate what the benefits are, when attempting to influence key stakeholders to approve unexpected preliminary work in the early days of the project.
  6. Be sensitive to the audience and make no assumptions about them having the same answers to any “whys”. Prepare, elicit, confirm, validate, and verify.

Though, setting the line that balances theory of “best practice” from the actual project approach is always risky and some people consider this an expensive misplaced academic exercise. But this can be mitigated by not ever losing sight of which artefacts need to be produced in the business analysis space.

The set of artefacts, and how they are framed up, should make evident how to translate the business needs into a feasible solution design and a relevant testing plan, in a traceable fashion. In the end: The BAs must support and influence the overall project WBS and the subsequent project plan.

The BABOK presents us a robust framework for business analysis, and those BAs who spent some time digesting its arid, but very logical content, sooner or later realise that its theory makes a lot of sense, thus it is an excellent base for any project approach.

Note: no framework, as sound as they can be, can perform the magic in transforming poor inputs in great outcomes….ooh should we refer back to missing why number 1?

There is very good material out there that cover the essential set of information that must be available when a business analysis plan is about to be compiled, yet I listed below some I consider key:

  • SMART objectives associated to the relevant business needs
  • Thorough stakeholder analysis
  • Current scope and how its changes will be managed (scope management)
  • Centralised source for project’s assumptions, constraints, risks, issues and dependencies
  • Performance metrics (current and expected) of the capabilities impacted by the project
  • Access to the documentation that was used to define the business needs listed in the business case
  • Business analysis artefact framework (organisational process assets) that will define the expected deliverables and their templates/standards. Ideally paired with the project work breakdown structure.
  • Business analysis plan template
  • Requirements management methodology

In conclusion, for a project to be deemed successful, it must convert the efforts of the allocated resources to something that ultimately adds value to the business. Part of that is filling in the answers to the missing “whys”, and adopting a pragmatic approach to deliver really good “BA stuff”!

Don’t forget to leave your comments below.

Women Have a Sixth Sense, Men Are Oblivious

I am a man, so I am completely qualified to say that men are oblivious. This is first demonstrated at a young age. Men, think back to when you were playing in the school yard and girls were chasing you. You had no clue the girl or girls chasing you liked you. I just witnessed this with my 10-year-old son. It was clear his classmate liked him and he was clueless. For men who have not embraced this quality, please do. That’s all I have to say about men. You all know what I am talking about.

On the other hand, women have a sixth sense. I am not a woman nor do I play one on TV. I do, however, have enough interactions with women that give me the ability to make this declaration. Many, if not all, women have an uncanny ability to read between the lines. Someone says something and they know the true meaning of the comments. Women can read an email and pick up on the subtle meaning of the sentences. Just as men are oblivious and can’t do anything about it, women too cannot control this trait. Someone says something, and they have this mental database of everything ever said by and about this person and form a hunch. The good thing is women are so in tune with your stakeholders and pick up on the smallest verbal inflections and non-verbal cues. (You may not have to read my last blog post.) The bad thing is that there are no clear facts to support their hunch. So sometimes a hunch or assumption is valid; sometimes it is wrong.

This is not to say men don’t pick up on cues or don’t have hunches and make assumptions. We are just genetically disposed to assume it has nothing to do with us. A few weeks ago I said something to a female friend and went on my merry way. The weekend came and went. On Wednesday of the following week we were having a conversation, and she apologized for being mad at me. Mad at me?! I could tell she was not happy, maybe even mad… just not mad at ME. I had no clue: oblivious. It turns out her reading between the lines was slightly off, and she made an assumption and ran with it. In this case her running was away from me because she was pissed.

In your communication with stakeholders, you need both of these traits. Sometimes you need to read between the lines and make assumptions. Other times you need the comfort of being oblivious and ask questions that many don’t ask because they assume they know the answer or assume they should know the answer and don’t want to look dumb.
Men, you need to focus on the subtle cues made by your stakeholders. You need to see when a stakeholder is frustrated, concerned, or not engaged with the project as needed. You then have to validate your assumption and actually consider how it is related to you or your team.

Women, keep it up and form those hunches. Just make sure you validate them and don’t assume a hunch is always accurate. Men have it a little easier—everyone knows we are oblivious. So, when a man asks, “Help me understand something” or “I’m not sure we are all on the same page” no one is surprised.

The situation where the benefit of obliviousness and a sixth sense comes in is when there is an “elephant in the room”. The elephant in the room is a problem that everyone knows is there but no one wants to acknowledge. As a leader on your team you need to expose and address the elephant. To even see there is an elephant in the room, you have to be in tune with your team or situation. But it’s not enough to stop there and assume that someone higher up the food chain will bring it up if it needs to be addressed. I don’t care where you are on the corporate food chain, you are a leader. It is your job to expose the elephant so it will be acknowledged and addressed. Here’s the thing, if you do nothing with the elephant you are viewed in one of two ways: You are really oblivious and don’t even know the elephant is there—not good. Or, you are viewed as too cowardly to address the situation—again, not good.

Be the best you can be by having the right level of obliviousness and a sixth sense.

All the best,

Kupe

Don’t forget to leave your comments below.

A Business Analyst’s Best Friends: The CIO

Successful BAs are the calm, center point of the project storm.  They evaluate the people, roles, systems, and processes swirling around them.   BAs find connections between the elements of the project storm.  They make sure all of the moving pieces align.

In order to maintain this alignment, BAs rely on strong relationships with many friends.  BAs need to anticipate their friends’ needs and learn how to influence cooperation. 

In January, I set the stage for a series describing the BA’s best friends.  This month’s friend is the CIO. 

How does the CIO benefit from a BA?

Here’s a scary thought:  The CIO knows who you are.  Yes, even if you work at a Fortune 500 company, it is likely the CIO knows you by name or reputation.

Here’s an even scarier thought: The CIO has seen your deliverables!  That big requirements document or that issue log or that PowerPoint presentation or that status report might make a journey all the way to the CIOs smart phone, laptop, or desk.   

Based on those thoughts, the CIO realizes the following benefits from a great BA:

  • Easy to Understand Deliverables
    • Use visuals: pictures, charts, diagrams 
    • Structure documents with summaries that introduce details
    • Highlight or prioritize the most important concepts or issues
    • Minimize jargon
  • Successful Projects
    • Meet the needs of stakeholders with minimal issues or rework
  • Bridge to Partners 
    • Build trusting and cooperative relationships with stakeholders

What makes a top-notch BA from the CIO’s perspective?

From the CIO’s perspective, a top-notch BA maximizes the value of the project.  What does this mean how do you do it?

For the sake of discussion lets define “value” as “a fair return”.  Like anyone, CIOs want to get a fair return on their money.  A CIO’s success hinges on the value he/she provides to the organization. 

BAs partner with stakeholders to define “value” for each project.   The “fair return” is the outcome of the project—does the solution meet the needs of the organization.  A top-notch BA maximizes value by using tools and techniques that:

  • Increase revenue, decrease costs, minimize or maximize risk to the organization
  • Improve accuracy:  requirements are correct and complete
  • Minimize rework:  Inspire an enduring solution that meets the needs of the stakeholders
  • Minimize maintenance:  Inspire a solution that minimizes ongoing support  

What frustrates a CIO about the BA role?

Remember the “scarier” thought above: CIOs see your deliverables.  Keep that in mind when you are creating requirements documents, issue logs, status reports, and presentations.  CIOs don’t have time for details.  They get frustrated by big, wordy, complex documents. 

So, assume that your documents will travel.  Do the hard work needed to simplify requirements.  Everyone will benefit.  Here are a few tips:

  • Use Appropriate Headings: Use headings that have business meaning and are understandable so that the reader (no matter what area or level) can predict what details are in that section of the document and decide effectively if they need and want to read the details.
  • Use Charts:  When you need to include details, group them in a chart or diagram. 
  • Use Pictures:  Use a picture to supplement or replace text. 
  • Create Decomposition and Summaries:  Prepare an executive summary for large or complex documents.  Focus on who, what, where, and when.  Minimize how. 
  • Use “white space”: Use white space on the document strategically to not overwhelm the reader with text or visuals that are too detailed. 

How to say no to a CIO?

Do you know your CIO’s name?  Have you met your CIO?  Do you chat with your CIO daily?  The relationship between a CIO and a BA varies based on the size and structure of an organization and the experience level of the BA. 

In most cases, a BA would not be in a position to say “NO” directly to a CIO.  Instead, a BA would supply information to the CIO via one of the CIO’s direct reports.  Prepare the direct report by outlining the consequences of possible decisions.  

For BAs that interact with the CIO directly, your best approach would be to challenge politely by asking questions.  

Always remember the CIO might be making decisions based on information you do not have and he/she cannot share. 

How to influence a CIO to get what you need?

Again, most BAs interact with CIOs through at least one layer of management.

All CIOs have goals and priorities for their organization.  BAs can work within the layers of management to understand the CIO’s priorities.  When BAs frame their needs in the context of the CIOs goals, BAs will have more influence. 

What’s most important to the CIO?  Here are a few possibilities: 

  • Value to the organization:  How will this bring value to our stakeholders?
  • Perception of IT:  Will this bring a positive perception of IT to the organization?
  • Bottom Line:  How will this affect my budget?  How will this increase profits? 
  • Service: How will this improve/hinder customer service?
  • Operations: How will this impact processes and procedures?  How will this improve quality? 
  • Morale: Will this lift morale?
  • Productivity: Will this decrease productivity?
  • Time to Market: How will this affect our delivery timelines?

How to communicate the value of the BA role to a CIO?

In many organizations, CIOs spend more of their budget keeping the lights on—maintaining, fixing, or enhancing existing systems.  That only leaves less than desired for strategic projects that have the power to shift the direction of the organization, innovate, and bring fun exciting projects to the organization.

Most CIOs and their business partners, want to flip their percentages and funnel more of their technology dollars to strategic projects.  Compared to maintenance projects, strategic projects provide more value to the organization—they are a vehicle for creativity and innovation.  CEOs and CIOs compare dollars spent in IT on “keeping the lights on” vs. strategic initiatives, there is constant pressure in the industry and internally to move these numbers in the right direction to move the organization forward.

I have worked with organizations where missed or inaccurate requirements led to fixes for fixes that were ten layers deep!  How many of your project originated as fixes to other projects?  How many layers of fixes have you seen?  We can as BAs change this and create more value to the organization by getting it right the first time!

I have seen BA talent reverse this trend and tip the scales in favor of strategic projects. 

Tell your CIO that great BAs create free space for strategic projects!  They get requirements right the first time—minimizing the need for fixes and enhancements.

What do you think? 

  • BAs:  Are you just keeping the lights on or are you creating free space for your CIO’s strategic projects? 
  • CIOs: Are your BAs helping your organization move forward?

Don’t forget to leave your comments below.