In short, you know when John is in the room and today he joins me for five questions about his career and his insights on being a Business Analyst.
You bring a lot of enthusiasm to your work, what motivates you as a BA?
I am a BA Enthusiast that is committed to getting the job done. I do this by managing both expectations and project constraints, which results in an atmosphere where project members feel proud of the result and ensure client expectations are exceeded. Our Process & BA Capability Lead, Scott Rainey, always says “Our Business Analysis Team is directly connected to the problem statement and the value from business case to implementation,” and it’s the truth! What also motivates me is seeing BAs come into their own going from an Entry-Level to a Junior Role, to a Senior Role – to Thought Leaders in their craft!
What positive trends are you seeing across your BA community of practice? And how are you addressing the challenges that inevitably arise in BA work?
What is trending majorly is the skills for BAs to understand, Data Management, Data Visualization, and Robotic Process Automation to help streamline activities for organizations. To help combat BA Challenges, we meet bi-weekly and discuss challenges and come up with solutions to help address those challenges. In our Community of Practice, all the BAs have a voice. Our CoP’s purpose is to provide a forum for continuous improvement of North Highland’s Business Analysis skillset through collaboration, mentoring, and education.
Throughout your career, you’ve worked across several different industries. How has your BA role varied from one to another?
BA roles differ in organizations because some organizations want BAs to focus on one thing (i.e. Process Mapping) when that’s only a subset of a skilled Business Analyst. BAs should be involved in multiple areas to truly provide value back to any organization.
What’s your favorite technique?
My favorite technique is the Scope Context Model helps describes the intended business change by helping stakeholders understand:
- How the solution contributes to the goals of the organization
- The expected, provable measures that indicate solution success
- When the solution is considered done
- Who will be consulted for requirements information
- Systems which might be impacted (or needed) by the proposed change
- Users of the intended solution and how they will interact with it
- Key assumptions, constraints and out of scope considerations
What project do you want to tackle next?
I would like to tackle a “game changing” effort that really pushes the needle for an organization that will benefit the industry and the BA’s role in its success.