Increasingly, organisations are choosing to outsource some functions or activities rather than develop the necessary capabilities in-house. This outsourcing might take a number of forms—at one end of the spectrum it might involve procuring an off-the-shelf cloud-based software package rather than attempting to build a similar solution from scratch. At the other end of the spectrum it might involve outsourcing a whole function or team to a managed service provider. On projects that implement this type of outsourcing, the artefacts that we’ll need to produce will vary, but it is common for a Request for Information (RFI) and Request for Proposal (RFP) to be issued. These documents help the client organisation to assess which vendors are interested and potentially suitable, whilst also providing the vendors with the opportunity to understand the client’s need so that they can put together a compelling and relevant proposal.
When writing an RFP, there are many considerations that need to be kept in mind. The document needs to outline the high-level solution requirements in a way that is succinct and digestible yet sufficiently detailed so that a vendor can provide a meaningful response. The client organisation will be interested in knowing to what extent their requirements can be met, and will be particularly interested in any areas where vendors may be lacking. For this reason, quite naturally and understandably, many RFP documents focus heavily on requirements.
As regular readers of my blog will know, I’m a real fan of Business Analysis conferences. I’ve always found that a good conference provides a melting-pot of ideas, and an opportunity for practitioners to get together and discuss developments in the BA profession. In a break from my normal blog style, I wanted to…
I want to let you in on a secret. One that I haven’t (up until now) told many people. Although I travel a lot with my work, I have never liked flying. Until a few years ago, I had an irrational fear of flying—to the point where I had a rather embarrassing ‘panic attack’ at an airport around 12 years ago—it really was quite spectacular for any onlookers! Although I’m now less scared of flying, I still absolutely hate turbulence. (And, incidentally, isn’t it ironic that the turbulence always seems to kick-in when the coffee is being served?)
I was travelling on a long-haul flight very recently, and was passing the time by doing what I like to call the ‘economy shuffle’. Perhaps you’ve done it yourself—it’s where you try to balance a laptop on the tray table, whilst sipping a coffee and eating a bagel—all without spilling anything, without nudging another passenger and trying to maintain some level of professional dignity in the process. It should be an Olympic sport—and it’s one that I would fail at spectacularly!
As I bit down into my breakfast bagel, I noticed a gentle beep of the fasten-seatbelt-sign coming on. The Captain came over the speakers:
“Just a quick update on our flight today. We’re making great progress, with a strong tailwind—however, we’re scheduled to hit some bumpy air very soon. We’re expecting it’ll be pretty rough, and we’re hitting it right where we expected to, so you’ll notice we’ve illuminated the ‘fasten seatbelts’ sign. We should be through it within 30 to 45 minutes, but we’ll keep you posted. Please return to your seats, and fasten your seatbelts with your tray tables folded and the armrests down.”
As ever in these situations, the Captain sounded calm—and the Cabin Crew went about their business checking that everything was in order. I shuffled my laptop back into my hand luggage, chugged down the remnants of my coffee and tried to relax. And boy was it a choppy flight — probably amongst the worst turbulence I’ve ever encountered — but I took some comfort in knowing it would only last for 45 minutes.
The plane landed safely a few hours later, and in the airport it dawned on me that I wasn’t scared, worried or panicked during the turbulence at all, which was great. I started to pull this idea apart and analyse it (well, I am a business analyst after all…). Why didn’t the turbulence bother me on this flight? Was it the whisky I’d had at the airport to calm my nerves? Whilst that might have been a contributing factor, on reflection I concluded that it all seemed more bearable because the Captain had warned us in advance and had given us the likely duration of the discomfort. I also presume he’d steered a course to minimise the turbulence, within the constraints of his flight path. The Captain had read the external environment well from his instruments, prepared his stakeholders (including passengers), and we’d all had a much better ride as a result.
As I wandered around the destination airport in a tired and jet-lagged state, it struck me how this pattern applies to business too. A crisis can be averted if it is predicted and carefully communicated and the right corrective manoeuvres are adopted. This relies on regular monitoring of the external business environment. Strategic environment analysis is a critical part of business analysis and should be considered an activity that is ‘business as usual’. External techniques like PESTLE or Porter’s 5-forces can be useful techniques. As businesses get more and more sophisticated and collect and collate more data and information, asking the question “How can we generate potential insight and testable hypotheses from our organisational data” becomes extremely important. Let’s face it, lack of data is rarely the problem, lack of analysis and actionable insight can be.
What this means for business and business analysis