Persona: What is a persona?

What is a persona?

A persona is a fictional archetype representing a group of users who share similar behaviours, goals and frustrations when using a digital product. Unlike a simple demographic profile, a persona is a rich portrait that includes motivations, digital habits, pain points and typical usage scenarios for a user segment. It is built from real data gathered through user research: interviews, questionnaires, behavioural analytics and field observation.

The persona concept was formalised by Alan Cooper in the late 1990s. Since then, it has become an essential tool in user-centred design. At Kern-IT, within the KERNWEB division, personas are created from the scoping phase of every web project. They serve as a compass for the entire team: designers, developers and content writers make decisions by asking how each persona would react.

Why personas matter

Personas transform abstract user data into tangible individuals with whom the entire team can empathise. This shift in perspective has profound consequences for the quality of the final product.

• User-centred decisions: when facing a design dilemma, the team can ask: "Would Marie, 42, a marketing director, understand this navigation?" This simple but powerful question prevents decisions based on personal opinions.
• Feature prioritisation: personas make it possible to rank features according to their impact on target users. What is useful for a secondary persona can wait for a later release.
• Experience consistency: a persona shared between designers, developers and writers ensures everyone is working for the same user. Tone of voice, interface complexity and technical detail level are calibrated accordingly.
• Client communication: personas facilitate exchanges with stakeholders. Presenting a design decision in reference to a persona is far more convincing than a purely technical argument.

How it works

Persona creation follows a rigorous process grounded in real data. At Kern-IT, we never create fictional personas disconnected from reality: every persona is anchored in observed data.

The first step is user research. This includes semi-structured interviews with target users (minimum five per segment), analysis of existing analytics data (Google Analytics, CRM data), quantitative questionnaires and direct observation of usage behaviours.

The data is then synthesised and clustered. The team identifies recurring patterns in behaviours, goals and frustrations. These patterns define two to four distinct user segments.

Each segment is then embodied in a persona document comprising: a first name and photo, demographic information, professional context, goals and motivations, frustrations and pain points, digital habits, a typical usage scenario and a representative quote.

Personas are finally shared and integrated into the design process. They are displayed in the workspace, referenced in design discussions and used as validation criteria during design reviews.

Concrete example

Kern-IT is commissioned to design the website of a Brussels-based professional training company. User research reveals three distinct segments.

The first persona is Sophie, 35, an HR manager in an SME. She is looking for training for her team, has a limited annual budget and needs to justify every expense to her management. She is frustrated by training sites that do not clearly display prices and funding options.

The second persona is Thomas, 28, a freelance developer. He wants to upskill continuously to stay competitive. He methodically compares offers, reads reviews and looks for flexible formats (e-learning, evening sessions). He is frustrated by complex registration processes.

The third persona is Catherine, 52, a CEO. She is seeking strategic training for herself and wants a premium experience. Price is not a deciding factor, but trainer quality and reputation are essential.

These three personas guide the entire site design: training pages include a visible price comparison (for Sophie), a review system and format filters (for Thomas) and detailed trainer profiles (for Catherine). The site is developed on Wagtail CMS with Tailwind CSS.

Implementation steps

1. Plan the research: define key questions, identify segments to explore and recruit five to eight participants per segment.
2. Conduct interviews: carry out semi-structured interviews of 30 to 45 minutes, recorded and transcribed.
3. Analyse the data: synthesise results, identify behavioural patterns and define segments.
4. Write the personas: create one document per persona with photo, context, goals, frustrations, typical scenario and quote.
5. Validate with stakeholders: present personas to the client to verify they match their understanding of the market.
6. Integrate into the process: use personas as a reference in all design, content and development decisions.

Related technologies and tools

• Figma: used by Kern-IT to create visual persona documents and share them with teams and clients within the project workspace.
• Google Analytics: a source of quantitative data on visitor behaviours, useful for enriching and validating personas.
• Wagtail CMS: the Django-based CMS whose admin interface is designed for non-technical profiles, in line with content editor personas.

Conclusion

Personas are far more than a design deliverable: they are the thread connecting every decision in a digital project. By embodying target users in concrete, documented profiles, they ensure the final product meets real market needs. At Kern-IT, the KERNWEB division regards personas as a foundational investment that determines the relevance of every wireframe, every design and every line of code.