Work, selected · Professional experience
The thinking, in practice.
Pick a case. See my contribution, then try one of the decisions behind it.
02 / Data migration assurance
A table is rarely
just a table.
During a data platform migration, I built metadata queries, dependency diagrams and tests around reporting requirements.
My contribution · Mapping · Reconciliation · Investigation · UAT & cutover support
Try a dependency
Choose an object. Follow the change.
Illustrative map and tests, independently created for this site.
One shared table, several questions.
Both reports depend on a shared transformation. Testing its inputs and its outputs helps connect technical checks to the questions people ask.
An illustrative test row
- The requirement
- What to compare
- If the results disagree
My contribution & delivery details
What I built
SQL metadata analysis, dependency visualisations and matrix-style tests, using report requirements to guide comparisons across SQL Server and Databricks.
What it informed
I shared the dependency analysis with the delivery team to inform validation and investigation.
Where I contributed
Mapping, reconciliation, discrepancy and defect investigation, UAT support and production-cutover activities within the wider programme.
03 / Business-process automation
The happy path is
only the beginning.
I sat with the business user, understood their recruitment process, then built an Outlook, Power Automate and SharePoint workflow around it.
My contribution · Discovery · Workflow design · Testing · User guidance
Try an exception
Give the workflow something awkward.
Guided illustrations of the design questions; no workplace system is connected.
- 01 · Check the input
- 02 · Preserve the documents
- 03 · Confirm completion
Two attachments. The same filename.
Two different applications each include a file called CV.pdf.
What could go wrong?
Saving both as CV.pdf in one location could overwrite a document or mix up applications.
The design decision
Use separate application destinations so both documents survive.
Check that both CVs remain available and each belongs to the correct application.
My contribution & delivery details
In use
The recruitment workflow is in use. Discovery, design and deliberate testing helped connect the automation to the team’s familiar process.
Adapted and tested
I later adapted the approach for a related workforce process, reaching a successful tested endpoint.
Made understandable
I translated the flow into plain-language visual guidance and walked users through it. Delivery included helping people understand what would happen and why.
04 / Visual documentation
Useful instructions.
A local tool.
IT procedures needed clear screenshots without sending account details or access settings to an external editor. I built a reusable PowerPoint annotation toolkit.
My contribution · Requirements awareness · Toolkit design · Wiki guidance
Take the toolkit
Clearer instructions. Yours to keep.
Paste a screenshot. Add markers, arrows, notes and covers. Export a clear instruction.
The PowerPoint toolkit is the original approach. The browser editor uses a fictional sample.
Use the .pptx in desktop PowerPoint. An offline browser edition is also available in the studio.
Show the action.
Keep the private details covered.
My contribution & delivery details
The requirement
Make visual instructions easy to create while keeping sensitive screenshots within the local editing process.
The choice
Use a familiar tool colleagues already had. Reusable markers, arrows, highlights and notes gave authors a consistent starting point.
The handover
Keep the working slide editable, then export a single annotated PNG for the Wiki. Reader and creator manuals explained how to use and maintain the documentation.
These accounts describe my contribution. Interactive examples are independently created; internal names, records, diagrams and code stay private.
Build with a real public dataset