02 — Process
Process
Design-led, marketing-fluent, systemic-minded with a pinch of automation · Respectful Vibe-Coder
I treat every brief like a product: who is it for, what does it need to do, how do we know it worked? Below is the loop I run, equally at home in design software as in a GTM brief.
- 01
Listen
Stakeholder interviews and co-design sessions, product deep dives, competitive read. No deck before the brief is sharp.
- 02
Frame
Translate the technical into a positioning that holds up in a sales call and a press release.
- 03
Make
Design the artefact (deck, one-pager, sales kit, interfaces, microsite, you name it!). Adobe InDesign, Illustrator, Premiere, PPTX, same premise: your need.
- 04
Automate
Templatize what repeats. Build systems, not deliverables — IT mindset baked in.
- 05
Measure
Pipeline, adoption, sentiment. Iterate the message with the same rigour as the product.
How I work
I sit comfortably in the space between teams (Admin, Strategy, Product, Sales, Engineering, Customer Relationship), translating in all directions and integrating towards the outcome. I've learned that the best marketing collateral doesn't come from a brief; it comes from understanding the product well enough to know what's actually worth highlighting.
That's one reason why I taught myself the technical side. I build my own automation flows and prototypes, out of sheer natural curiosity, but also I can talk to and support engineers, and so the decks, one-pagers, and launch materials I create are grounded in how the product really works and embed the creative meaning of it.
My method, briefly: understand deeply, structure ruthlessly, communicate simply. Workshops to extract the truth. Systems thinking to organize it. Design to make it land.
A few automation flows I built and ship in production — proof, not theory.
