About

A good digital solution rarely starts in the code. It starts in a concept and a brand, in what the organisation wants to say and to whom.

I have worked across that whole chain: from sales and planning to structure, UX and development, and on to content, operations and maintenance. Communication, design and technology affect each other all the time. It is the whole that decides whether a solution holds up over time. That is why I look at a solution from several sides at once: what the client needs, what users expect and what can be built and maintained.

Background

My background is in the communications industry, with clients in both the private and public sectors. UX has been part of everything I have done: in the structure, in the interfaces and in how editors work with the solutions after launch. Content work gave me the understanding of users. Code gave me the tools to turn it into interfaces, and experience with backend lets me see early what can be built.

I am not a specialist in any single part. I work where the project needs me and adapt how I work to the client, the project and the conditions. My skills come from experience across many projects rather than from one particular method, and I am keen to learn new things.

InPublix, a platform for digital annual reports that I initiated and built at the agency, has been in production with paying clients for more than ten years.

Right now

I am taking that experience into a new context. New technology and AI are changing every step, from idea and structure to design, code and maintenance. Solutions can be produced faster than ever. That makes it more important to judge early what is right to build and to set the right priorities from the start. That is where experience makes the difference. I call it Competence Value: domain knowledge, systems understanding and judgement govern how the tools are used.

I started using AI in client work at the agency: Codex and Cursor in development, ChatGPT for research, structure, UX and content. Since July 2026 I have been working on my own development projects where AI is used in every step, but under control. Product requirements, specifications and tests decide what gets built and how it is checked. Design prompts and a shared design system mean that design and code start from the same ground. It works in both directions: design becomes code, and modules from the code can be brought back into the design. Figma has long been part of my work, mainly from a technical perspective, for components, design proposals and the transition between design and code. In my own projects I also work with Claude Design and Claude Code.

Content Studio shows where this leads. At its core it is a way of working: a bridge between communication, information architecture, UX design and technology. The people who write, design and develop work in parallel against the same modules and design system, without being locked to a particular platform. The tools support the process and hold it together. The idea comes straight from experience of how agency projects actually work, and today it exists as a concept with a first pilot.

The point is not to take the craft out of design work. I am exploring new paths: what works and what does not, where the limits are and how AI tools are best used. AI should complement human judgement and work, not replace it.

I am going deep into modern web development with React, Next.js, TypeScript and Node.js. Since autumn 2026 I also work with Umbraco and .NET, focused on headless.

The next assignment or role is where web development meets UX: from structure, wireframes and prototypes to design systems, accessible interfaces and code that holds up.