discovery-requirements/
2022-24
Discovery & requirements
I turn user needs into requirements a delivery team can work from.
UX research · stakeholder workshops
- user research
- requirements
- delivery review
the problem
People describe the same service from different perspectives. The design needs a clear account of what each person is trying to do.
approach
- I use research and workshops to understand needs, constraints and competing priorities.
- I turn findings into user journeys, content needs and requirements that people can discuss together.
- I review delivery against agreed requirements and explain where a design needs another pass.
$ tail -n1 field.log
- Good discovery gives a team a shared question to answer. I try to make that question precise before proposing a solution.
survey-design/
2022-25
Questions that produce usable data
I connect research questions, bilingual questionnaires and the structure of the resulting data.
Questionnaire design · routing logic
- survey design
- data quality
- research
the problem
A questionnaire needs to produce answers that can be interpreted and used for a clear purpose.
approach
- I work from the research question to the wording of each item and the data it should produce.
- I design bilingual questions and routing that account for different respondents.
- I define how answers relate to measures and work with specialists on validation.
$ tail -n1 field.log
- The quality of a dataset starts with the questions and definitions that produced it.
data-definitions/
2024-25
Data definitions that hold up
I clarify what a measure means before building the reporting around it.
Data modelling · reporting requirements
- data definition
- data lineage
- reporting
the problem
A number is difficult to interpret when the definition underneath it is unclear.
approach
- I make definitions explicit and work through the cases at their boundaries.
- I trace how a definition affects the data collected and the measures built from it.
- I explain the reasoning so technical and nontechnical contributors can review the same rules.
$ tail -n1 field.log
- I look for the definition behind a disagreement about numbers. That habit also helps me ask clearer questions about information handling and responsibility.
ai-governance/
2024-present
Responsible AI adoption
I help teams connect AI ambitions with clear requirements, responsibilities and questions about data use.
Coordination · governance contribution
- AI governance
- requirements
- coordination
the problem
An AI initiative needs a defined purpose and people who can make and follow through on decisions.
approach
- I bring research and requirements work into discussions about where AI can be useful.
- I contribute to governance work by helping make responsibilities and data-use questions explicit.
- I coordinate across disciplines and keep agreed decisions and follow-up visible.
$ tail -n1 field.log
- My contribution combines coordination and governance. I am also developing the technical side of applied AI.
service-journeys/
2024-25
Service journeys people can follow
I map a service from the first question to the final step, then work through the points of friction.
Research · journey mapping
- UX research
- journey mapping
- service design
the problem
A sequence that makes sense to a delivery team may still be difficult for the person using it.
approach
- I research how people approach a task and where they need help.
- I map the journey and redesign the flow around what a person needs at each step.
- I use the map to bring contributors into the same discussion about the service.
$ tail -n1 field.log
- A clear journey is a useful way to discuss trade-offs. It makes the consequences of a decision easier for everyone to see.
registration-design/
2024-25
Registration and interface design
I translate service requirements into forms and interfaces that people can follow.
UX · interface design
- registration
- interface design
- requirements
the problem
Registration has to balance the information a service needs with the effort it asks of the user.
approach
- I organise the steps around the task a person is trying to complete.
- I connect interface decisions with the research and requirements behind them.
- I review the flow as a whole, including where people need an explanation or a next step.
llm-workflows/
2025
Automation & LLM workflows
I connect workflow logic, APIs and language models, with attention to the data each step uses.
Workflow design · API integration
- automation
- REST APIs
- LLM workflows
approach
- My implementation experience includes connecting APIs and webhooks into workflows.
- I bring data-quality questions into the work alongside the tooling.
- I use cross-functional discussions to connect the technical workflow with the process around it.
$ tail -n1 field.log
- I am developing this practice further through applied AI and software engineering.
workshops-requirements/
2022-24
From workshops to requirements
I help people turn different perspectives into a shared account of what needs to happen.
Facilitation · business analysis
- facilitation
- business analysis
- communication
approach
- I structure discussions around the purpose of a service and the needs of its users.
- I translate the discussion into requirements and flows that can be reviewed.
- I keep open questions visible so a workshop leads to useful follow-up.
common-core/
2021-25
42 Common Core
Peer-reviewed projects in C, C++ and Unix, from a shell and concurrent programs to networked services and containerised applications.
Engineering education · completed alongside the job
outcome
Common Core completed to Level 10 in May 2025, at 42 Abu Dhabi.
the problem
Develop a practical foundation in systems programming, networking and full-stack web development.
approach
- minishell and Philosophers for Unix internals, process control and concurrency.
- NetPractice and ft_irc for networking and protocol work, Born2beroot for administering and hardening a Linux virtual machine, Inception for containerisation.
- cub3d and ft_transcendence for graphics and full-stack web, so the core was not only systems.
$ ls stack/
c c++ unix docker tcp/ip
$ tail -n2 field.log
- Systems programming, networking and Linux administration give my developing cybersecurity practice a technical foundation. These projects are engineering education.
- Alongside that technical foundation, I bring research, requirements, data governance and cross-functional coordination from my professional work.
Back to the crossing ←
Read my CV →