Business Analyst

IX Solutions

5d•Remote

About The Position

As a Business Analyst at IX Solutions, you will be responsible for business-level discovery, process and operating-model analysis, requirements definition, prerequisite identification, and decision support for client projects and advisory engagements. This role serves as a crucial link between stakeholder needs, operating requirements, governance considerations, and technical prerequisites, translating them into clear planning inputs for effective solution delivery. You will lead discovery and planning discussions with both business and technical stakeholders, clarifying desired outcomes and success metrics, documenting requirements and dependencies, and ensuring alignment between business needs and implementation results throughout the project lifecycle. Collaboration with Account Executives, Solutions Engineers, Architects, Consultants, Project Managers, and IT Managers is key to ensuring project direction is firmly rooted in clear requirements, ownership, and delivery readiness. The position reports to the Director, Client Solutions and involves a 40-hour work week, typically between 8:00 am and 4:30 pm or 8:30 am and 5:00 pm, Monday to Friday. Balancing multiple client priorities and deadlines is essential, with occasional after-hours availability required. This role is ideal for a structured, curious, and business-savvy facilitator capable of transforming stakeholder input into precise requirements, practical process guidance, defined prerequisites, and actionable handoffs for technical and delivery teams. IX Solutions is dedicated to employee growth and development, and responsibilities may be adjusted to align with individual goals and business objectives.

Requirements

3-5 years of relevant experience in business analysis, requirements gathering, process analysis, project delivery, technology consulting, operations, or a related role.
Demonstrated ability to facilitate discovery sessions, clarify requirements, and document decisions with business and technical stakeholders.
Strong understanding of business process mapping, current-state and future-state analysis, acceptance criteria, dependencies, and project handoffs.
Comfortable supporting projects involving Microsoft 365, SharePoint, Power Platform, automation, business intelligence, security, cloud, infrastructure, resilience, or similar business technology environments.
Excellent written and verbal communication skills with both technical and non-technical stakeholders.
Strong analytical and problem-solving skills with the ability to identify options, risks, trade-offs, prerequisites, and unresolved decisions.
Detail-oriented, organized, business-aware, and comfortable balancing structured documentation with practical delivery needs.
Proficient with Microsoft Office and common collaboration, documentation, diagramming, project, and requirements-management tools.
Legally permitted to work within Canada.
Hold a valid Driver’s License and vehicle.
Ability to speak and write English fluently.
Be able to travel occasionally for business purposes.
Reside in Alberta or British Columbia, Canada.

Responsibilities

Lead discovery and planning workshops with business and technical stakeholders, creating a clear structure for the conversation and keeping discussion focused on business outcomes, delivery needs, and decisions required to move forward.
Develop a strong working understanding of the client’s business context in the areas being analyzed, including relevant processes, stakeholder needs, operating constraints, decision points, and success measures.
Gather and clarify business requirements, desired outcomes, constraints, and key decisions needed to guide project or initiative direction.
Turn discovery findings, stakeholder input, current-state issues, and operating constraints into clear requirements and planning direction for technical and delivery teams.
Connect requirements and process decisions to the business outcomes the client is trying to achieve within the engagement.
Separate confirmed requirements from preferences, open questions, assumptions, and unresolved decisions to reduce ambiguity before work moves into design or delivery.
Document decisions, ownership, acceptance criteria, dependencies, and required follow-up actions in a format that supports delivery execution and stakeholder accountability.
Maintain alignment between business requirements and implementation outcomes throughout delivery by revisiting requirements when scope, design direction, or client priorities change.
Map current-state and future-state business processes where process change, workflow improvement, automation, or operational handoff is part of the engagement.
Identify business, operational, governance, data, security, resilience, and support requirements that affect project direction, delivery readiness, or long-term usability.
Help define business-level models such as access control, information classification, recovery expectations, approval flows, and privileged access operations where those models are required for project success.
Clarify how people, process, controls, ownership, and support expectations should shape the technical outcome, including how the solution will be used and supported after implementation.
Surface gaps between the client’s current operating model and the future-state process so stakeholders can make informed decisions before delivery assumptions become embedded.
Identify blockers, risks, and unresolved decisions that may affect delivery readiness, adoption, supportability, or project success.
Support architecture and design activities by turning business requirements into clear planning inputs that help technical teams make appropriate design and implementation decisions.
Define prerequisites, dependencies, constraints, ownership, and decision points required for successful delivery, including items that must be confirmed by the client before work can proceed.
Maintain client and engagement context across advisory, sales, technical, project, and managed-services teams so important requirements, decisions, and constraints are not lost during handoff.
Prepare structured handoffs that help technical and delivery teams understand requirements, acceptance criteria, risks, decisions, stakeholder context, and known dependencies.
Support projects involving AI, SharePoint, Power Platform, automation, business intelligence, security, cloud, infrastructure, and business and technology resilience by helping define the business and operating requirements behind the technical work.
Work with Solutions Engineering, Architects, Consultants, Project Managers, and IT Managers to maintain a shared understanding of project direction, client expectations, scope boundaries, and delivery risks.
Stay engaged during delivery where needed to clarify intent, confirm whether proposed changes still meet the business requirement, and help resolve requirement-related questions.
Facilitate business and technical conversations in a structured, clear, and outcome-focused way, helping stakeholders move from discussion to decisions.
Ask clear questions that separate stated requests from requirements, constraints, risks, operating impacts, and decisions needed for delivery.
Communicate clearly with clients and internal teams in writing, workshops, meetings, and delivery discussions, adapting the level of detail to the audience and purpose.
Summarize stakeholder input, open questions, and required decisions in a way that supports action, accountability, and follow-through.
Keep stakeholders aligned when priorities, requirements, or delivery constraints shift, ensuring the impact of those changes is understood before decisions are made.
Support ambiguous or sensitive stakeholder conversations where requirements, trade-offs, ownership, or delivery direction need to be clarified.
Create clear, usable documentation for requirements, process flows, decisions, dependencies, acceptance criteria, and delivery handoffs.
Maintain accurate notes and project artifacts that support continuity across advisory, technical, project, and managed-services teams.
Organize information so that clients and internal teams can see what has been decided, what remains open, who owns follow-up, and what must happen next.
Identify recurring discovery, requirements, process, and handoff patterns that can improve IX Solutions’ templates, delivery practices, and advisory capability.
Contribute to templates, checklists, workshop approaches, and reusable planning materials that improve consistency and delivery readiness.
Use delivery feedback to improve how requirements are captured, documented, communicated, and transitioned into technical work.