Interview: DSCRT Group Owner¶
Stakeholder: Group operational leadership with process ownership and cross-functional coordination responsibilities
Date Conducted: [To be filled]
Interviewer(s): [To be filled]
Notetaker: [To be filled]
PREPARATION¶
Goals (Doelen)¶
What do we want to achieve with this interview?
- Understand the operational workflow and how process ownership is distributed across the group
- Identify handoff points, ownership boundaries, and recurring friction between teams or functions
- Validate the process map at the operational level (vs. strategic level from ECC GM)
- Gather evidence about what information is lost, duplicated, or misunderstood in current handoffs
- Establish the operational constraints and dependencies that shape feasibility of any compliance solution
- Map concrete examples of workflow pain points and their impact on team efficiency
Success Criteria:
- Stakeholder confirms we have mapped the major workflow stages and handoff points
- We have identified at least 3 recurring pain points or rework loops in the current process
- We understand which teams own which parts of the compliance process and where boundaries blur
- We have concrete examples or metrics showing the impact of process friction
Roles (Rollen)¶
Who is involved and what are their responsibilities?
- Interviewer: Research lead responsible for diving into operational detail, probing handoff logic, and capturing bottleneck evidence
- Notetaker: Captures process steps, team roles, pain point details, rework loops, and any process diagrams or metrics shared
- DSCRT Group Owner (Subject): Provides operational perspective on workflow, team coordination, process friction, and constraint visibility
- Optional Observers: If permitted, a representative from a downstream team (DevOps, audit, security) to provide cross-functional perspective
Pre-Interview Coordination:
- Confirm availability and duration (suggest 75–105 minutes for deeper operational dive)
- Request permission to record or take detailed notes
- Ask stakeholder to think of a recent example of compliance work or process change to walk through in detail
- Offer to provide a preliminary process map based on prior interviews for feedback
Topics (Onderwerpen)¶
What will we ask? What themes will we explore?
Theme 1: Operational Workflow and Team Structure¶
- Walk me through a typical compliance-related task or decision from start to finish in your group
- Who are the key roles involved at each step, and who owns each step?
- How do tasks move between teams or functions?
- What information needs to be communicated at each handoff, and how is it currently communicated?
Theme 2: Handoffs and Boundaries¶
- Where do most misunderstandings or delays occur between teams?
- Are there any handoff points where work gets stuck waiting for approval, information, or clarification?
- How clear are the ownership boundaries when a task spans multiple teams?
- What happens when there's ambiguity about who owns a particular step?
Theme 3: Rework and Friction¶
- Can you give me an example of a recent task that had to be reworked or sent back?
- How often does that happen, and what are the most common reasons?
- What is the typical cycle time for a compliance-related decision or evidence artifact?
- Where in the process is the most time spent, and is it on value-added work or wait time?
Theme 4: Information and Evidence Flow¶
- What information artifacts flow through your workflow (e.g., checklists, audit logs, policy documents, approval records)?
- How are these artifacts created, shared, and validated?
- Are there duplicate efforts to gather or verify information across teams?
- What information is currently difficult to access or reconstruct?
Theme 5: Constraints and Dependencies¶
- What external systems or tools must any compliance solution integrate with?
- Are there organizational policies or union agreements that constrain how work can be structured?
- What resource constraints (budget, staffing, skills) affect your ability to improve the current process?
Theme 6: Metrics and Success¶
- How do you currently measure the health of the compliance workflow (speed, accuracy, stakeholder satisfaction)?
- What would improvement look like in terms you can measure?
Procedures (Procedures)¶
Where, when, how long, and with what logistics?
- Location: [To be determined — in-person preferred for collaborative diagram/whiteboard work; virtual with screen-sharing acceptable]
- Duration: 75–105 minutes (confirm availability; request focus time without interruption)
- Recording/Notes: [Explicit permission requested; notetaker present; optional whiteboard photos/screen captures]
- Setup: Space suitable for workflow discussion; whiteboard or collaborative tool helpful for mapping process steps; access to any reference documents (process diagrams, recent task examples)
- Follow-Up: Schedule follow-up confirmation call (30–45 min) within 1 week to validate process map and confirm pain-point impact
- Artifacts to Bring: Process flowcharts, task templates, recent example of a compliance task (anonymized if needed), team org chart, any existing metrics on cycle time or rework frequency
EXECUTION¶
Pre-Interview Checklist¶
- Date, time, and location confirmed with stakeholder
- Recording/note-taking permission secured
- Agenda shared; stakeholder asked to prepare example task walkthrough
- Preliminary process map prepared (if available from prior interviews) for stakeholder feedback
- Notetaker briefed on key themes, pain-point targets, and team structure context
- Whiteboard, sketch tool, or collaborative document prepared for collaborative mapping
Interview Notes¶
[Record workflow steps, handoff details, pain points, team roles, and artifacts mentioned below.]
Date: [To be filled]
Attendees:
Opening Remarks/Context from Stakeholder:
Theme 1: Operational Workflow and Team Structure
Findings:
Process Steps / Team Roles Identified:
Evidence/Artifacts Mentioned:
Theme 2: Handoffs and Boundaries
Findings:
Boundary Clarifications / Ownership Questions:
Evidence/Artifacts Mentioned:
Theme 3: Rework and Friction
Findings:
Specific Rework Examples:
Evidence/Artifacts Mentioned:
Theme 4: Information and Evidence Flow
Findings:
Information Artifacts Identified:
Evidence/Artifacts Mentioned:
Theme 5: Constraints and Dependencies
Findings:
System/Tool Dependencies:
Organizational Constraints:
Evidence/Artifacts Mentioned:
Theme 6: Metrics and Success
Findings:
Current Metrics / Success Indicators:
Evidence/Artifacts Mentioned:
Post-Interview Analysis¶
Key Findings¶
[Synthesize operational workflow, handoff logic, and pain-point patterns that inform SQ0/SQ1 evidence.]
Identified Pain Points¶
- [Description, teams involved, impact, frequency/severity]
- [Description, teams involved, impact, frequency/severity]
- [Description, teams involved, impact, frequency/severity]
Process Map Validation¶
- Current workflow steps confirmed / clarified
- Team roles and ownership boundaries documented
- Handoff points and information flows mapped
- Bottleneck locations identified
Evidence Collected¶
- Process workflow diagram or task walkthrough (captured / to be requested)
- Team structure and role descriptions (confirmed / to be requested)
- Examples of compliance-related tasks and rework instances (documented / to be requested)
- Metrics on cycle time, rework frequency, or team satisfaction (provided / to be requested)
- List of system integrations or tool dependencies (provided / to be requested)
- Other: [Specify]
Mapping to Research Questions¶
SQ0 (Existing Work):
- What did we learn about current operational processes and how compliance work is performed?
- What tools, methods, or practices are currently in use, and where are the gaps?
SQ1 (Meta-Model Definition):
- What attributes must the meta-model capture to represent the operational workflow accurately?
- What organizational and process constraints must the meta-model respect or accommodate?
- What information needs to flow between teams, and how should the meta-model support that?
Follow-Up Items¶
- Item: [Action], Owner: [Name], Due: [Date]
- Item: [Action], Owner: [Name], Due: [Date]
- Item: [Action], Owner: [Name], Due: [Date]
Next Steps¶
[Describe how findings inform next interview or research step.]