01Week 1
Discovery and scope
Stakeholders, current workflow, target workflow, success criteria, owners, risks, and required data.
Independent implementation exercise
Implementation Delivery Pack
A practical example of how I would take a Satiaphic workspace from discovery to go-live. It is based on the working product and its real rules, but it is not presented as a completed external client engagement.
Implementation plan
A controlled path from kickoff to launch
02Week 2
Configuration and data
Workspace, roles, intake channels, notification rules, integrations, and validated import mapping.
03Week 3
UAT and training
Role-based test scripts, issue register, administrator walkthrough, and end-user practice.
04Week 4
Go-live and handoff
Readiness decision, production checks, launch support, open-issue ownership, and support handoff.
Discovery brief
What must be understood before configuration
The kickoff would identify the business owner, workspace administrator, daily users, current feedback sources, review responsibilities, required history, access restrictions, launch date, and support owner. Decisions and unresolved questions would be recorded with named owners rather than left in meeting notes.
Success criteria
- SC-01Every imported feedback record belongs to the correct workspace and retains its source.
- SC-02Owners, administrators, and members can complete only the actions allowed for their roles.
- SC-03Public links, QR forms, embedded forms, and connected reviews enter the same review workflow.
- SC-04A user can trace a work item back through its theme or proposal to the original feedback.
- SC-05Billing access changes only after a verified provider event.
Configuration matrix
Business decisions mapped to system setup
Configuration is recorded so the customer and delivery team can verify what was agreed before UAT.
| Area | Decision required | Configured result |
|---|---|---|
| Workspace | Business identity, language, timezone, plan | Workspace settings and tenant-scoped data |
| Users and access | Owner, administrator, member | Role assignment and permission checks |
| Feedback intake | Public link, QR code, embed, Google reviews | Channel setup and source attribution |
| Workflow | Priority, status, assignee, themes, proposals | Shared operating rules and ownership |
| Notifications | Invitations, assignments, status changes | Email and in-product notification rules |
| Billing | Plan and subscription state | Verified DodoPayments event handling |
Data migration and validation
A repeatable import mapping
A sample CSV import would be tested first. Source totals, accepted rows, rejected rows, duplicates, and workspace assignment would be reconciled before approving a production import.
| Source field | Satiaphic field | Validation |
|---|---|---|
| External ID | sourceReference | Required; unique within the source |
| Feedback text | content | Required; reject blank values |
| Submitted at | createdAt | Parse date and flag invalid formats |
| Source | source.type | Map to review, link, QR, embed, or manual |
| Rating | rating | Optional; accept only supported range |
| Customer name | authorName | Optional; preserve privacy rules |
User acceptance testing
Tests written in the user’s language
UAT-01Submit feedback from a public channelRecord appears in the intended workspace with the correct source.
UAT-02Attempt a restricted action as a memberThe action is blocked and workspace data remains unchanged.
UAT-03Create follow-up work from feedbackThe work item retains a traceable link to its source feedback.
UAT-04Process an invalid billing eventSubscription access does not change.
UAT-05Switch between Arabic and EnglishEquivalent content loads and the Arabic layout uses right-to-left direction.
Go-live readiness
Go or no-go checks
- Production environment variables and service credentials are present and separated from development.
- Workspace owner and initial user roles have been confirmed.
- Intake channels, email delivery, scheduled jobs, and external events have been checked.
- Critical UAT issues are closed; accepted lower-priority issues have an owner and target date.
- Import totals and rejected rows have been reconciled before production use.
- Administrator training, support route, escalation details, and rollback responsibility are agreed.
Training and handoff
Users leave knowing what to do
Administrators: workspace settings, channels, members, permissions, billing, and issue escalation.
Daily users: inbox review, assignment, priority, themes, proposals, and work-item follow-up.
Handoff: configuration record, unresolved issues, known workarounds, support contacts, and ownership after launch.
Support and escalation
Issues arrive with enough context to act
CriticalService unavailable, cross-workspace exposure, or billing access failureImmediate escalation with reproduction steps, impact, logs, and owner
HighCore workflow blocked for multiple usersTriage, workaround if available, and engineering escalation
NormalSingle-user issue, question, or non-blocking defectDocument, resolve or schedule, then add recurring answers to the guide
Working product