My single most important recommendation to anyone considering the use of outside consultants is simple: Get everything in writing! Clearly define the work assignment, get a signed agreement spelling out the terms of the assignment, and demand regular status reports.

I am always amazed how companies give consulting firms carte blanche to perform project work as they see fit. Abdicating total control to a consultant is not only irresponsible, it is highly suspicious and may represent collusion and kickbacks.

There is nothing magical in managing consultants. It requires nothing more than simple planning, organization, and control. If you are not willing to do this, then do not be surprised with the results produced. Failure to manage a consultant properly or to adequately inspect work in progress will produce inadequate results. So, do yourself (and your company) a favor, do your homework and create a win-win scenario for both the consultant and yourself.

As a business analyst, navigating groupthink is essential for delivering valuable insights and driving successful projects. By fostering a culture of inclusivity, promoting diverse perspectives, and encouraging critical thinking, business analysts can overcome the challenges of groupthink. Remember, effective negotiation of groupthink empowers teams to make informed decisions, enhances problem-solving capabilities, and ultimately contributes to improved project outcomes. Embrace these strategies, and you'll be well-equipped to lead your team towards successful and innovative solutions.

This is no different from the technology dilemma that many BAs find themselves in as they work to advance their BA career. There is no way you can learn everything at one time, but you can take gradual steps to continue to advance your skills.  So don't fear, I am here with some tips on how to approach this dilemma and lessen some of that overwhelm that plaques business analyst. And I truly believe the reason this is a stress is because you want to stay relevant in the field of business analysis if you are currently in a BA role or working to obtain a BA role.

Natural Language Processing (NLP) is a branch of artificial intelligence that aims to allow machines to comprehend, interpret, and generate human language. It comprises developing algorithms and models capable of processing natural language input such as text, voice, and pictures in order to do activities traditionally performed by humans. Recent developments in machine learning technology, as well as the availability of large natural language datasets, have allowed NLP to make great strides in recent years. Quality checks, extraction, classification of requirements, requirements modeling, traceability of requirements, and retrieval are the six main areas of focus for NLP tools and studies. In this article, I discuss these advances in NLP for requirements engineering (RE). NLP for requirements engineering is a growing field of study, yet there is a disconnect between research findings and practice. This is because there aren’t enough high-quality data sources and domain-specific requirements sources. Despite this, scientific progress has been made in showing potential. The community of practitioners should collaborate with academics and tool suppliers to influence the direction of NPL for RE.

Process Mining is a subject that has garnered a lot of attention over the past two to three years. Much of the noise has centred around the mergers and acquisitions in the vendor space, and contrary to what some write, it is still in its infancy when it comes to end user adoption.

Some academics and industry analysts suggest that Process Mining is a technique that replaces the need for traditional business and process analysis, but this is never likely to be the case. Instead Process Mining and its closely related cousin Task Mining, are complementary to traditional approaches, and should be thought of in the context of “and” rather than “or”.

For the past 30 or more years we have increasingly applied automation to processes, both with and without proper documentation. The result is that many of the processes we use, business decisions taken, rules applied, and customer journeys are now embedded or hidden within systems. This cloak of “invisibility” makes it practically impossible for us to apply traditional analysis techniques to discover and analyse these rules, processes decisions and journeys.