Business Analyst

A selection of business analysis work focused on understanding complex operational problems, identifying requirements and dependencies, mapping processes, aligning technical and business stakeholders, and translating findings into actionable improvements. Details are generalized to protect confidential systems and processes.

Requirements & Process Analysis

Process Analysis

Analyzing Production Failures to Redesign Change Management

Business Problem

Production changes were contributing to recurring incidents, but the organization needed more than individual technical fixes. The underlying release process had to be analyzed to determine where operational risk was entering the workflow.

Analysis & Discovery

  • Reviewed recurring incident patterns and their relationship to production changes.
  • Examined release timing, readiness, testing, rollback planning, and ownership.
  • Worked across Engineering, SRE, QA, and technology leadership to identify process gaps.
  • Distinguished isolated technical failures from repeatable workflow problems.

Requirements & Recommendations

  • Formal go/no-go decision points before production changes.
  • Clearer release-readiness criteria.
  • Defined rollback expectations.
  • Earlier identification of QA, access, and dependency requirements.
  • Stronger Change Advisory Board governance.
7–12 → 3–4 weekly production incidents following broader change-management and SRE process improvements.
Workflow Analysis

Analyzing and Automating a Documentation Workflow

Business Problem

Documentation publication and maintenance status depended on manually gathering information from sprint-board tasks, creating repetitive administrative work and reducing visibility into upcoming needs.

Analysis & Discovery

  • Mapped the existing workflow from task creation through publication and maintenance.
  • Identified which information was already available in the sprint board.
  • Separated necessary human decisions from repetitive data collection.
  • Defined the information editors needed to track status and upcoming work.

Solution

Designed and implemented a Power Automate workflow that pulled task information into the team’s publication and maintenance tracking process.

Outcome

Reduced manual tracking work and created a more repeatable process for understanding documentation status and future maintenance needs.

Systems & Dependency Analysis

Systems Analysis

Mapping Enterprise System Dependencies

Business Problem

Major third-party outages exposed limited visibility into how external services connected to internal applications and business workflows. When a provider failed, downstream impact had to be discovered during the incident.

Analysis & Discovery

  • Identified system owners and subject-matter experts across technology teams.
  • Gathered information about upstream and downstream dependencies.
  • Connected technical services to the applications and workflows relying on them.
  • Identified missing ownership and dependency information.
  • Documented relationships so impact could be evaluated across systems rather than one application at a time.

Business Value

Created better visibility into third-party and cross-system risk, supporting faster impact analysis and more proactive outage planning.

Data Analysis

Investigating Cross-System Data Mismatches

Business Problem

Users encountered inconsistent information across connected systems, requiring analysis to determine whether the issue originated with source data, synchronization, processing, or downstream presentation.

Analysis Approach

  • Compared expected and observed information across systems.
  • Identified the systems and teams participating in the data flow.
  • Traced where information diverged within the workflow.
  • Coordinated technical investigation across responsible teams.
  • Translated technical findings into understandable operational impact.

Outcome

Narrowed the investigation from a broad user-facing problem to the specific system interaction requiring correction, reducing unnecessary troubleshooting across unrelated components.

Risk & Gap Analysis

Business Rules

Analyzing Identity Impersonation Workflows

Business Problem

Potential impersonation incidents required a consistent method for determining whether suspicious activity represented a legitimate relationship, a technical issue, or a case requiring formal escalation.

Analysis & Decision Logic

  • Reviewed the reported activity and available relationship information.
  • Verified whether the involved contact had a legitimate trusted relationship.
  • Separated cases that could be resolved operationally from those requiring additional escalation.
  • Applied defined escalation criteria to qualified incidents.
  • Coordinated escalation to Legal when appropriate.

Business Value

Created a repeatable triage path that connected operational investigation with business risk and formal escalation requirements.

Gap Analysis

Identifying Gaps in Automated Detection

Business Problem

Some suspicious activity was being identified through manual investigation rather than existing automated detection, indicating a gap between real-world scenarios and the criteria used by the detection process.

Analysis & Discovery

  • Reviewed incidents that were not captured automatically.
  • Compared observed behavior with existing detection criteria.
  • Identified patterns that required manual recognition.
  • Documented findings from operational investigations.
  • Fed those findings back into discussions around detection criteria and process improvement.

Business Value

Turned individual incident findings into reusable information for improving how future suspicious activity could be identified.

Stakeholder & Readiness Analysis

Requirements Discovery

Identifying Requirements Before Major Production Changes

Business Problem

Major production changes could move toward implementation before every participating technical team had the access, environments, or information required to support the change safely.

Discovery & Stakeholder Analysis

  • Reviewed proposed changes through Change Advisory Board discussions.
  • Identified teams responsible for validation and post-release support.
  • Asked whether required QA and developer access was already available.
  • Surfaced readiness gaps before the production change occurred.
  • Coordinated with stakeholders to ensure missing prerequisites were addressed.

Outcome

Helped ensure two technology teams had the QA and developer access needed before major changes, reducing avoidable implementation and support risk.

Impact Analysis

Tracing Production Impact Across Third-Party Dependencies

Business Problem

Production failures sometimes appeared to originate internally even when the underlying change occurred within a third-party service, making ownership and impact difficult to determine quickly.

Analysis Approach

  • Reviewed the affected workflow from the user-facing symptom backward.
  • Compared internal deployment activity with vendor-side changes.
  • Identified the external dependency participating in the failed transaction.
  • Coordinated findings across Engineering, SRE, operations, and vendor stakeholders.
  • Documented the dependency for future incident and readiness analysis.

Business Value

Improved the ability to distinguish internal defects from third-party failures and strengthened visibility into vendor dependencies affecting production workflows.

Additional workflow examples, process documentation, and analysis artifacts are available upon request.