Start typing and press enter to search
Start typing and press enter to search
Most of us have heard of the pirate, Blackbeard, real name Edward Teach. Born around 1680 in Bristol, England, Teach rose to infamy sailing his ship the Queen Anne's Revenge in the early 18th century.
Blackbeard epitomised the art of taking risks and embracing imperfection. In May 1718, along with his fiercely loyal crew he blockaded Charleston, one of the busiest ports in the American colonies. Employing bold tactics, Blackbeard took ships and their cargo hostage which significantly disrupted maritime trade. His unconventional approach influenced a change in naval warfare.
While Blackbeard used his skills for questionable means, there’s much that we as Business Analysts can learn from him.
I’ve created a Business Analysts Pirate Code, inspired by stories of piracy through the years.
Pirates thrived by taking bold, calculated risks. Similarly, as business analysts we can benefit from embracing action over analysis paralysis or waiting on stakeholders.
You don’t have all the information? Waiting on decisions? No problem - make an informed assumption, communicate it and keep sailing forwards.
Pirates often lived by their own codes, adapting traditional rules to suit their needs. Business analysts can do the same by questioning outdated practices and creating new ways of solving problems.
Use your experience of other organisations, industries, projects or techniques to pave a way forwards.
I’m a huge fan of taking multiple idea’s and smashing them together - it’s not in the textbook, but it sure is more fun!
Pirates were experts in navigating unpredictability. Business analysts need the same level of adaptability when dealing with shifting client needs, market changes, or project pivots.
Changes are not bad, they are in fact quite normal and we need to be ok to flex within the changes. Our job is to ensure the ship can navigate safely through the change, sometimes that's avoiding it, but often it’ll be hitting the waves head on and riding out the storm.
Pirates depended on loyalty within their crew. Business analysts who build trust and loyalty with their teams and stakeholders create the strongest, collaborative relationships.
Stay present, stay visible. To build trust and loyalty there really is nothing quite like being physically present whenever possible. Check in on key stakeholders, challenge their thinking in private and support them in public.
Pirates shared the spoils of their conquests. Business analysts should adopt a mindset of sharing knowledge, insights, and credit with others.
We don’t just deliver a project and move on, we create real meaningful value and we help to grow capability, leaving a lasting legacy wherever we set sail.
Pirates often seized opportunities that others overlooked. Similarly, business analysts should develop the ability to spot hidden potential in projects and with organisations.
Keep your ear to the ground, build your network, ask the follow up questions and BE CURIOUS.
Not only will it help you uncover hidden gems related to your project, but you could help to identify new ways to create value. Look out for the inefficiencies, the missed chances. If you’re not sure it's worth highlighting - remember rule 5.
Embrace your inner pirate, don’t be concerned about what the textbook says - a pirate wouldn’t. Use the business analyst's pirate code to be bold, to embrace the challenging situations and nurture your crew of project ship mates. It’s all about finding the buried treasure chest (that’s creating value to the non pirates amongst you).
The project seas are incredibly unpredictable, the pirate code reminds us that sometimes, the best way forwards is to chart our own course.
Have you got any great examples where you’ve embraced any of these rules?
What Pirate Rules would you add?
Link copied to clipboard
.png)
