Gemotest · Healthcare / Medical IT

Analysis Canvas

Reconstructed evidence of cross-system employee-lifecycle analysis, from process and system boundaries to target-state design.

What this proves

Decompose a cross-system workflow before automation decisions

Best fit
Enterprise BA · Process Analyst · Business Systems Analyst
Verified anchor
10,000+ scope · ~30% less manual work in target workflows
Boundary
Reconstructed model; scope and target-workflow result stay explicit.

Reconstructed from confirmed work. Not an original employer diagram. Production topology and confidential process detail are omitted.

Evidence trace

Process → Systems → Rules & dependencies → Target state

  1. 01
    Process

    Make the end-to-end employee lifecycle visible before discussing automation.

  2. 02
    Systems

    Separate workflow logic from the systems and interactions that participate.

  3. 03
    Rules & dependencies

    Expose triggers, blockers, dependencies and manual hand-offs.

  4. 04
    Target state

    Turn the current-state model into a controlled future-state workflow.

Reconstructed analysis model

From a broad workflow to four inspectable questions

The goal was to make a cross-system employee lifecycle easier to reason about before defining a target state.

01

Process

Question: What actually happens across the employee lifecycle?

  • Hire
  • Employee changes
  • Offboarding
Analysis focus: make the end-to-end sequence visible before discussing automation.
02

Systems

Question: Which systems participate, and where does each interaction belong?

  • 1C ZUP
  • Active Directory
  • Exchange
  • Core platform
Analysis focus: separate process logic from system ownership and interactions.
03

Rules & dependencies

Question: What triggers the next action, and what can block or break the flow?

  • Requirements
  • Cross-system dependencies
  • Triggers / blockers
  • Manual hand-offs
Analysis focus: expose the conditions that make the workflow reliable or fragile.
04

Target state

Question: Which manual steps can be simplified or automated without losing control?

  • Target workflows
  • Simplification opportunities
  • Automation candidates
  • Alignment around the future state
Analysis focus: move from “what exists” to a controlled future-state workflow.
Claim boundary

What this artifact supports — and what it does not

Supported
  • Cross-system employee-lifecycle analysis
  • 1C ZUP, Active Directory, Exchange and core-system interactions in scope
  • 10,000+ employees in process scope
  • Approximately 30% less manual work in target workflows
Not claimed
  • Original employer diagram or exact production topology
  • Implementation ownership across every participating system
  • 10,000+ as personal output rather than process scope
  • ~30% as an independently measured personal KPI outside the target-workflow context
Continue

Continue through the evidence.

Next move

Want to discuss the analysis behind it?

I can walk through what is confirmed, what was reconstructed for the portfolio and where the claim boundary sits.