In the fast-paced world of corporate strategy, projects often fail not because the technology is broken, but because the human element is forgotten. In Episode 124 of the Harmonious Workplaces podcast, hosts Rich Cruz (an organizational development consultant) and Ben Kleinman (known playfully as the “czar of change management”) dive deep into how organizations can bridge this gap. Specifically, they explore the critical intersection of Business Analysis (BA) and Organizational Change Management (OCM), discussing how these two functions can collaborate to make workplace transitions smoother, more effective, and more enjoyable.
Unpacking the “Acronym Soup” of Project Delivery
Before diving into the core discussion, the hosts playfully unpack the “acronym soup” that dominates corporate initiatives—ranging from PMs (project, product, or program managers) and HR (human resources) to complex systems like CRMs (customer relationship management) and ERPs (enterprise resource planning).
To set a clear baseline, they define the fundamental tasks of a Business Analyst:
- Elicitation: Gathering needs and expectations directly from stakeholders.
- Requirements Analysis: Documenting both functional and non-functional system needs.
- Process Mapping: Outlining how work gets done, often utilizing frameworks like BPMN (Business Process Model and Notation) to create flow diagrams.
- Solution Assessment: Evaluating proposed options (such as analyzing whether to build a greenfield system from scratch or buy and configure an off-the-shelf solution) to ensure they deliver a strong return on investment (ROI).
BA vs. OCM: Technical Solutions vs. The People Side of Change
A major theme of the episode is the distinction—and the overlap—between the technical solution and the people side of change.
A Business Analyst is traditionally focused on delivering the technical part of the solution, ensuring that a new process, software, or machine meets specific, detailed business requirements. They analyze internal “as-is” processes, look at PESTEL forces (political, economical, societal, environmental, and legal), and SWOT alignments (strengths, weaknesses, opportunities, and threats) to build the business case.
Conversely, Change Management (OCM) practitioners focus on the people side of change. They determine who is impacted, how they are impacted, and what those humans need to successfully adapt to and sustain the new way of working.
As Ben points out, asking a single person to handle both highly technical requirements gathering and the delicate human components of change might simply be “asking too much”. Instead, having a dedicated OCM practitioner work alongside the project manager and BA ensures that the human experience is not ignored.
The RIASEC Personality Clash: CIE vs. SIE
To explain why these roles attract different types of professionals, Rich introduces John Holland’s RIASEC model (Realistic, Investigative, Artistic, Social, Enterprising, Conventional), which is widely used by the U.S. government for career profiling.
According to Rich’s analysis:
- Business Analysts typically align with the CIE profile (Conventional, Investigative, Enterprising). They thrive on conventional data, structured systems, and technical details.
- Change Practitioners lean toward the SIE profile (Social, Investigative, Enterprising), often with an Artistic bent to handle creative, interpersonal interventions. They possess a stronger social orientation.
Despite these personality differences, both roles share a critical superpower: the ability to translate. BAs translate stakeholder needs into functional technical specifications, while change managers translate personal transitions, struggles, and resistance into actionable support strategies. Both roles require empathy and the ability to sit in multiple worlds.
How AI is Transforming the Business Analyst Role
The hosts also tackle a burning question: How does artificial intelligence (AI) impact the world of business analysis?
AI agents are rapidly becoming powerful assistants. They can analyze survey data, ingest meeting transcripts or video recordings to extract stakeholder needs, draft business cases, and even auto-generate process flow diagrams.
Rich shares a real-world story where his team used Copilot during elicitation sessions to ingest dozens of “as-is” processes, compare them to “to-be” models, and perform rapid gap analyses. In this specific project, the BA’s process mapping unearthed a “shadow organization”—a retired-bound employee who was acting as a secret, undocumented human connector between finance/accounting and other departments. By using AI for gap analysis, the change management team could see exactly what risk was present and prepare to mitigate the impact of her retirement.
However, both hosts agree that AI will not completely replace human BAs or change practitioners. AI lacks the ability to pick up on critical human nuances—such as body language, tone of voice, unspoken fears, and the subtle cues that indicate whether a team has truly bought into a change.
The Ultimate Takeaway: Don’t Shortchange Business Analysis
The core message of Ep. 124 is simple: do not shortchange business analysis. Whether you hire a dedicated BA or train existing team members in BA methodologies, taking the time to conduct thorough requirements gathering and stakeholder analysis before developing a strategy is vital to transitioning harmoniously from point A to point B.
Have a laugh and a reflection with Hermie the HR Hermit Crab cartoons.
0 Comments