Skip to main content

Tag: Skills

The Better Meeting Manifesto – Stop Having Terrible Meetings!

Terrible meetings are an unfortunate feature of modern working life.  It doesn’t have to be this way: read on to find out how you can take a stand and achieve better meetings for all!

 

Encountering a terrible meeting in the wild

Most of us have suffered through a terrible meeting.  You know the scenario.  A group has assembled in an airless meeting room in response to a calendar invitation.  The AV equipment is faulty, so the unlucky person with the controls has spent the past 10 minutes trying to connect to the remote attendees.  Everyone else is making small talk or discussing the previous meeting.  When the equipment finally cooperates, you all realise that the meeting organiser isn’t in attendance.  Undeterred, you check the meeting invitation – only to find it unhelpfully blank.  The group makes a valiant attempt to progress things; however, you can only get so far with the main person missing.  The meeting finishes early; the group sighs and agrees to reconvene another day.

 

Then there is the alternative, more insidious variant.  At first glance, things begin well: the meeting logistics are on point, the right people are in the room, and you received the outline ahead of time.  Yet once the meeting starts, issues soon become apparent.  There are too many items for discussion.  Due to aggressive timeboxing, there is little scope for more than brief comments regarding each.  People grow increasingly frustrated with the lack of opportunity for input, the schedule drifts, the meeting overruns and several agenda items are never reached.  The group makes little progress; the attendees are sentenced to a re-match to address the same material the following week.

 

Regrettably, these experiences are far from rare.  Is it little wonder, then, that we sometimes find it hard to get our stakeholders to make time in their diaries for yet another meeting?

 

Trojan horse meetings: a false solution

To combat meeting aversion, some session organizers resort to subterfuge.  One such ploy is the classic Trojan horse maneuver: book meetings into the calendar under the guise of something more palatable.  Often, the decoy is a workshop.  For example, a document sign-off meeting might be billed as a ‘requirement sign-off workshop’, even though the session is less about facilitated qualitative review and more about sitting around a table together to agree that the ensuing work can proceed.  A stakeholder interview to elicit information about a particular aspect of their role might appear in the calendar as a ‘process workshop’.  A team meeting might become a ‘team workshop’, and so on.

 

Superficially, this tactic can bear fruit – at least in the short term.  So why do people feel more positive about workshops over meetings?

 

  • Meeting fatigue

The first reason is novelty, pure and simple.  People want respite from busy calendars booked up with tedious and unproductive meetings.  Workshops are attractive because they generally feature interactive activities instead of the usual dry discourse.  Even the mere hint of this variety can suffice to lure stakeholders into believing they are in for a welcome change.

 

  • Productivity by association

A workshop is a facilitated intervention that seeks constructive input from all attendees to achieve a defined output.  In positioning their meeting as a workshop, the organiser aims to appropriate the qualities of focused, engaged participation and demonstrable productivity from the workshop format and confer them upon their meeting session.

 

Unfortunately, the aspiration of engagement and productivity will only get you so far.  Without good facilitation, a meeting will still be terrible no matter how you dress it up.  Worse: a bad ‘workshop-but-actually-a-meeting’ experience might harm your work by putting stakeholders off attending workshops in the future.

 

Advertisement

 

Another way

Rather than deflecting attention from the problem, it’s time to take a long, hard stare at the meetings in our lives.  Faced with a wilderness of terrible meetings, how can we act to change things for the better, no matter which end of the calendar invitation we are on?

 

  1. Make meetings pointy

All meetings should have a clearly defined purpose and intended outcome.  No point?  No meeting.


As the organizer:

If you are responsible for setting up a meeting but cannot answer the questions ‘Why are we meeting?’ and ‘What should we have achieved by the end of the meeting?’, this is a sign that you should reconsider.  Is a meeting necessary, or might there be another way to work with your stakeholders (e.g. using your organisation’s preferred collaboration tool)?  Don’t be afraid to postpone or cancel a meeting if circumstances change.

 

As an attendee:

Your time is as valuable as anyone else’s.  Invitations are not obligations.  If you receive a vague meeting invitation, contact the organizer and politely ask them to clarify the meeting’s purpose.  A helpful sentence to use is ‘Please could you confirm what will be covered in this meeting so that I can prepare?’ – it helps you sound engaged while also acting as a prompt for the organizer to step up their game.

 

  1. Energize and engage

Meetings can’t always be fun, but don’t make them any more painful than they have to be.  Start with the intended outcome and take active responsibility for getting there.

 

As the organizer:

A great tip from BA guru Angela Wick is to ‘verb-noun’ your meeting titles to set the intention for the session outcome: instead of ‘Requirements Review Meeting’, try ‘Finalise Requirements for Procurement’.  It instantly puts your attendees into a more active mode of thinking which will carry into the meeting itself.  Set a clear schedule with realistic timings and manage the session actively to keep things on track.  Don’t let people doze off: check in frequently with all attendees (particularly those attending remotely) to ensure that everyone feels involved and has the opportunity to provide input, even if it’s just a quick thumbs-up/thumbs-down vote.

 

As an attendee:

It might not be your meeting, but you are part of it – and its success or failure.  Help things go smoothly by doing any necessary pre-work ahead of time and coming to the meeting prepared.  Be fully present and listen actively – nobody wants to recap points made five minutes ago because you were not paying attention.  Consider whether your comments contribute usefully to the intended outcome before speaking.  Where you can, support the facilitator.  For example, can you help by relaying remote attendees’ comments to the room?

  1. Master your meeting modes

Following the recent pandemic, many of us continue to work flexibly between the office and home; meetings now frequently mix face-to-face and remote attendance.  These ‘hybrid’ sessions can be tricky to get right, but it’s not impossible.  With a bit of planning, you can be a meeting mode superstar.

 

As the organiser:

Meet your stakeholders where they are.  If people are uncomfortable with coming into an office space, forcing an in-person meeting will result in no-shows.  Save face-to-face for the times you truly need it and focus on providing a good experience online for everything else.  Be aware that attendees may decide to group up and attend online from the same room, so give specific instructions if your planned activities require each person to have separate access to a computer.  Design for online: take full advantage of the synchronous and asynchronous collaboration tools available through the applications at your disposal.  Get equipment warmed up in plenty of time, ready to get going when the meeting starts.  And whatever you do: don’t apologise or make excuses!  You’re about to lead a fantastic online session, after all.

 

As an attendee:

If you are attending in person, don’t forget to acknowledge and address any people attending remotely.  As a remote attendee, be mindful of your audio input.  Use a quality headset with a good microphone if you work in a shared office environment – and be prepared to mute yourself when you aren’t speaking to minimise disruption.  Nothing is worse than hearing background noise or someone thundering away at their keyboard.

 

What tips and tricks have you found to tackle the tyranny of terrible meetings?  I’d love to hear your thoughts!

To BA or Not To BA: Why Every Team Needs Business Analysts

The importance of having a business analyst (BA) on your team can’t be overstated. Acting as the bridge between stakeholders and technical teams, the BA wears many different hats. On any given day, a BA can be expected to work on a number of different tasks, whether that’s defining business cases, validating solutions, or even working with data (See this article on the role of BAs in an increasingly data-driven landscape). Able to straddle both worlds and speak the language of businesspeople and techies alike, BAs really are one of the most versatile members of the team.

 

The Story of an Ask

Many businesses are concerned with their ideal state, while the nitty gritties of how to actually get there are very much back of mind. “Often, the client is not able to fully explain what business problem they wish to solve and how to translate their business requirement into language the technical teams can understand,” explains Lizande Botha, a BBD project manager for a major financial services client in Africa “which is why BAs are a vital part of the process”. Put simply, BAs are responsible for translating a business ask into detailed requirements that can be understood and actioned by technical teams.

But how do we get to this point, when the ask itself is unclear? “The first question I tell the BA to ask the client is: What is the problem we’re trying to solve?” explains Botha, adding that the cardinal role of the BA is to ensure that the client ask is clearly defined. “For clients who really are unsure of what it is they want, the BA needs to keep digging and asking questions to truly get to the core of the problem” she adds.

 

Advertisement

 

Once this key piece of information has been gathered, the BA can start drilling down into the different possible solutions, what the budget is for the project, and other confines or expectations the client might have. Understanding the requirements and clearly defining the scope of any given project from the get-go can be make or break – so much so that CIO magazine reports that up to 71% of failed software projects can be attributed to poor requirements. Thus, consulting with a BA at the start of a project can avoid potential stumbling blocks.

While this early engagement is vital, the job of the BA doesn’t start and end there. Leveraging rapport built with business stakeholders, they must check in regularly to provide progress updates, while ensuring that on the engineering side things are running on course and to the requirements of the client’s business. They’re even able to partake in platform or application testing. Truly, the BA’s impact is felt throughout the project lifecycle!

 

BBD’s Drive to Help and Resolve

BBD’s teams are all complemented with BAs who are well equipped with experience and a thorough understanding of the industry they’re operating in. As each industry offers complexities unique to its environment, BBD strives to best match their analysts to sectors where they can bring their experience and real-life learnings to the table, explains Botha. This is a high priority for BBD, a software solutions company which delivers software solutions for clients across the industry spectrum, from financial, education, public sector, gaming, and beyond. Assigning BA’s that already understand the nuances, jargon and processes of a particular industry enable us to expedite the solution process” says Botha

But beyond managing teams to ensure the best hands are on board, BBD is ready to tackle any problems their clients have. And when it comes to understanding what those problems are, BBD has BAs on call to bridge the client-engineer gap and ensure the success of all of their solutions.

Looking for a software partner to help you on your next ask? Get in touch with BBD.

 

Best of BATimes: Business Analyst Jobseeking tips – Acing The Interview

Published on: January 7, 2021

The business and economic environment is incredibly tough right now, and I know from conversations with some of my connections that it’s a tricky time to be a BA jobseeker.

 

Competition is rife and it can be a challenge to know how to really shine in a job interview.

I recently facilitated a webinar panel session with Michelle Shakesheff and Saffron House (two senior BA managers) on this very topic.  This article summarizes some key takeaways from that session, with a few of my own thoughts added in for good measure.  It’s important to keep in mind that I’m based in the UK, so I’ll be reflecting on the expectations for job interviews here—I am sure expectations differ across the world so be sure to check out other articles and resources too.

Preparation Is Everything

When it comes to a job interview, preparation is everything.  There are many aspects that need to be considered, including the three ‘Rs’: Research, Role & Rehearsal.

Firstly, if you’re serious about working for a particular organization, then it’s crucial to research it.  This doesn’t have to be time-consuming, can be entirely ‘desk-based’ and is an opportunity to use a range of strategic business analysis tools.  You’ll want to check out the organization’s website, if it’s a large organization it’ll probably have an annual report.  What is its stated mission and strategic objectives? What are its stated values? Techniques such as VMOST can be useful for helping us to understand where a company is heading.  Approaches such as STEEPLE are excellent for brainstorming external factors that might affect the organization.  You might want to assess what you consider to be the biggest external opportunities and threats to the organization.  Utilizing these (and other) techniques alongside general research will provide a picture of the types of project that a company is likely to be undertaking.  You’ll pick up the language of the industry and organization, you’ll be well-placed to give specific answers to any strategic questions that the interviewer asks even if these don’t crop up, you’ll be well-placed to ask a relevant question about the organization’s strategy.  You’ll also get a sense of whether this is a company that you’d fit into and actually want to work for!

Secondly, there’s the role. Read every detail of the job description, person specification and whatever artefacts you can get your hands on.  Think back to your experience and be prepared to give an example for every skill or competency that is listed.   One senior manager I used to work with always advocated creating a table to systematically work through a job description, breaking it down into its component parts and adding an example against each.  If you do this, you’ll have the right example on the tip-of-your-tongue and won’t hesitate if a question crops up.  Here’s an example:

Requirement on job spec

My example

My contribution

The outcome

Process modeling & analysis

XYZ Project: analyzed 25 processes, proposed improvements. Used BPMN.

Led process discovery, as-is and to-be modeling. Resolved conflict through workshopping.

All processes were implemented. Stakeholders loved the new processes as they’d been involved throughout.

Resolving conflict

ABC Project: Removal of permanent desks.

Ran a prototyping session so ‘hot desking’ workers could see the benefits.

Stakeholders who were reluctant became advocates.

Analyzing business rules

Etc.

Etc.

Etc…

Finally, there’s the rehearsal.  I remember hearing polar explorer Allan Chambers speak over a decade ago.  He gave the sage advice ‘never take your body somewhere your mind hasn’t been’.  This applies for interviews too: take your mind to the interview room (or virtual interview room).  Imagine the types of questions you might encounter, formulate your response, and say them out loud.  What is the first thing you’ll say to the interviewer?  You’ll get different questions on the day, of course, but you’ll feel more confident and prepared and your answers will likely be slicker and well-informed.   This brings us neatly to our next topic, questions.

 

Advertisement

 

There Are No “Top Ten” Interview Question Lists

Although this might sound disappointing, there really aren’t any “standard” BA interview questions.  There might be patterns that crop up, but the questions are going to vary depending on the specific requirements for the role.  It’s also highly likely that there won’t be a “right answer” to any particular question—put yourself in the shoes of the interviewer and think what are they trying to understand from this question?  And don’t be afraid to ask for clarification.  It is genuinely hard to create unambiguous interview questions, and speaking personally, whenever I’ve been involved with interviewing candidates I take requests for clarification as an extremely positive thing. After all, BAs ought to be clarity-seekers!

It’s also important to answer the question that’s asked, not the one that you might have hoped the interviewer has asked.  I’ve fallen into this trap myself in the past, and I can tell you it doesn’t end well… However, if you’ve considered the different areas of the job specification and have examples for each area you’ll be well prepared to pivot and adapt on-the-fly.

A word of warning here. One trait that seems to be common amongst most BAs I’ve ever met (myself included) is the tendency to say “we”.  As BAs we work with others, and a success is a team success.  This is fine in most circumstances, but job interviews are a place to say I as well as we.   By all means discuss what the team achieved, but remember the job interviewer is going to want to know what you contributing.  Hearing “We created and prioritized a backlog” is interesting.  Hearing “I worked with the PO and coached them on the user story format. We experimented with different formats, but settled on user stories with some attached scenarios and acceptance criteria, which I wrote on behalf of the PO…” is more useful.  Precision is great.

Talking of precision, frameworks can act as a common language.  Being familiar with industry frameworks such as IIBA’s Business Analysis Body of Knowledge guide (or whichever is relevant for your context) can help.  Using industry standard terminology such as requirements elicitation, strategy analysis, requirements lifecycle management and many, many more besides will help ensure that you and the interviewer are on the same page.  Of course, it’s likely that the organization will have its own internal framework.  If you’ve been able to learn about that in advance through your research, then use those terms too.

Remember: An Interview Is Two-Way

It might seem like an interview is purely for the employer, but this is far from the truth.  It’s also you’re opportunity to assess whether the organization is a good fit for you.  Do the interviewers treat you respectfully?  Do they keep failing to turn up for the interview at the last minute without explaining why and then re-arranging?  Keep in mind that an employer that treats candidates without due respect may well treat employees similarly.

On the flip side, you may well find you get on fantastically with the interviewers, and all of your instincts are that this is the job for you.  Be sure to take the opportunity to ask the interviewer questions too.  You might ask them about the size of the team, the challenges they are facing—this might be a chance to showcase the research that you’ve done and ask them a specific question about the strategic direction of the organization and how it impacts the BA team.  Choose the right questions for the context, and use it to learn about the organization and the role.

Conclusion

Job interviews are nerve-wracking, but those nerves push us to prepare and perform well.  Remembering the three Rs: Research, Role & Rehearsal, thinking about the questions that might be asked and remembering an interview is a two-way process can help.

The Importance of Creativity in Business Analysis

Being creative may seem contradictory to an analyst structured approach to everyday tasks but this is far away from truth. Creativity is something required in every aspect of our life. Although, a deterministic approach is synonymous to analysis and decisions are being made using careful research, still there is much room for creativity.

In the business analysis field, the aim of developing creativity as a skill is to provide value to the whole business analysis lifecycle and to contribute not only to better outputs but also to significant outcomes.

Below are just some occasions when creativity can be required from a business analyst:

 

  1. Creativity is required in finding the best way to elicit the actual business needs. You may modify and tailor an elicitation technique in order to achieve the most accurate and helpful results from elicitation activities. A creative business analyst will pose “clever” questions in order to better understand the customer. Will continuously modify predefined techniques in order to tailor them in accordance with the context and the special needs of the stakeholders.

 

  1. In case there is not a predefined product that will be used, and the solution is built from the scratch, creativity is detrimental in order to find feasibly solutions that will provide value to the end users.

 

Advertisement

 

  1. Business analysts advocate for the business while communicating what can be achieved with available technology. The way business analyst will transfer the information from one side to another requires creativity. Providing a bridge between technical and business viewpoints is sometimes challenging. Unorthodox ways of presentation and communication of the information may be the key.

 

  1. Drawing out additional meaning from the elicitation results requires creativity resulting from a creative dispute mindset. Asking what the actual need of the customer is and how might the end user has defined the success imply sometimes filling information gaps using creative thinking.

Creativity skills can be learned and improved throughout professional life.  What you first need is a desire to explore your unique creativity and a spirit of curiosity. Just ask yourself and try to come up with creative ideas in your everyday tasks.  The most important is to be critical against conventional wisdom and try always to take into consideration the context in order to tailor and use wisely the conventional wisdom.

The Importance of Creativity in Business Analysis

Being creative may seem contradictory to an analyst structured approach to everyday tasks but this is far away from truth. Creativity is something required in every aspect of our life. Although, a deterministic approach is synonymous to analysis and decisions are being made using careful research, still there is much room for creativity.

In the business analysis field, the aim of developing creativity as a skill is to provide value to the whole business analysis lifecycle and to contribute not only to better outputs but also to significant outcomes.

Below are just some occasions when creativity can be required from a business analyst:

  1. Creativity is required in finding the best way to elicit the actual business needs. You may modify and tailor an elicitation technique in order to achieve the most accurate and helpful results from elicitation activities. A creative business analyst will pose “clever” questions in order to better understand the customer. Will continuously modify predefined techniques in order to tailor them in accordance with the context and the special needs of the stakeholders.

 

  1. In case there is not a predefined product that will be used, and the solution is bult from the scratch, creativity is detrimental in order to find feasibly solutions that will provide value to the end users.

 

Advertisement

 

  1. Business analysts advocate for the business while communicating what can be achieved with available technology. They way business analyst will transfer the information from one side to another requires creativity. Providing a bridge between technical and business viewpoints is sometimes challenging. Unorthodox ways of presentation and communication of the information may be the key.

 

  1. Drawing out additional meaning from the elicitation results requires creativity resulting from a creative dispute mindset. Asking what the actual need of the customer is and how might the end user has defined the success imply sometimes filling information gaps using creative thinking.

 

Creativity skills can be learned and improved throughout professional life.  What you first need is a desire to explore your unique creativity and a spirit of curiosity. Just ask yourself and try to come up with creative ideas in your everyday tasks.  The most important is to be critical against conventional wisdom and try always to take into consideration the context in order to tailor and use wisely the conventional wisdom.