Hi, I'm Dayo.

Here's a bit more about who I am and how I think.

Where it started

A hand-drawn pyramid diagram sketched by Dayo, ranking Owners, Builders, Internal & External Consultants, Prompt Engineers, and Observers

I stumbled on computers because my dad bought a personal computer for the house. From that machine I learned Paint, CorelDraw, and Photoshop, then went to school to study design because I'd fallen in love with it.

From childhood I always liked drawing, sketching, illustrating ideas. I just didn't know for a long time that it was something I could actually do.

Why I design the way I do

Aside from design, I'm a certified behavioural change practitioner. Understanding the people who use a product, not just the product, reveals their real desires, needs and fears. That instinct carries into everything I design.

Dayo with his two children at Glasgow Botanic Gardens

Sovereign by David Elikwu resting on Dayo's own handwritten notebook, open to process notes on methodology and skills

A perpetual learner

I'm exploring how AI can help me build experiences that feel great, not just look right. I also read several books at once, chasing answers to specific questions rather than one at a time: currently Sovereign by David Elikwu, The Tyranny of Merit, and Raising Good Humans.

Outside design

When I'm not designing, I'm tinkering with some technology or tool, bouncing ideas with someone, sketching, taking notes, or making content.

I've also led design at multiple companies, and ran my own company for 8+ years. I carry that into community work too: a Canva Empower Community Canvassador (2023–2025), running free Canva training sessions, including one for Braunstone Town Council in Leicester.

Process, tools, and how AI fits into my design workflow.

.claude/skills/design-practice/└── skills/    ├── session-log/    ├── design-brief/    ├── information-architecture/    ├── design-tokens/    ├── process-meeting/    ├── frontend-design/    ├── skill-patch/    ├── accessibility-review/    ├── senior-design-review/   · Published    └── persuasive-microcopy/   · Published

I manage AI locally, using folders and plain .md files as context. Follows the Interpretable Context Methodology (ICM): folder structure as agent architecture.

I used to have ideas for how a product should work, then need someone else to build them. Now, with AI and ICM, I can release those ideas myself. This portfolio is proof: designed in Figma, built with Claude Code in VS Code.