Menu Zamknij

An easy way to verify how effective
your Parliament deputy is.


An easy way to verify how effective your Parliament deputy is.


Please note

The project was designed for Polish users, therefore wireframes are in Polish.

My role

  • Conducting research.
  • Creating product strategy.
  • Designing prototype.


Problems to solve

  • Difficulty in checking how effective are elected deputies.
  • Not knowing what deputies are currently working on.
  • Being more aware when choosing a candidate to vote for.

In-depth interviews (IDI)

The goal of the interviews was to check is there a need to verify the work of parliament deputies. I also wanted to know what methods were used by the respondents for such verification. Besides asking about parliament deputies, I also asked about representatives in local governments. In total I conducted 6 interviews preceded with the recruitment process.

Respondent screening requirements:

  • Active voter
  • Good to know what civil society is;
  • Optional: activist;

General research questions:

  • From which sources do you collect information about politicians?
  • How much effort would you put into finding information about a politician?
  • How do you find out what your local government or deputy has done?
  • How do you define a reliable source of information?
  • What methods of dialogue with a local government do you know? When would you use them?
Because it matters who that person (candidate) is,
also in private - he must be ethical.


Based on the data from Individual In-Depth Interviews, I created Persons. They served as a guide in making decisions. When defining persona, Information about its motivation or goals were much more useful than demographic data.

Personas description (in Polish)

Value Proposition Canvas

In order to define the product values important for the user, I used the VPC. This method also allowed me, to determine whether the product has a chance to respond to the user's problems. I filled out the sheet with the User-Driven approach (from right to left) because I had a lot of information about the user and no existing product.
During the work, it turned out that the application can achieve various goals, so it was necessary to clearly define priorities and mark side goals.

The application will answer the following needs:
  • create a sense of well-made decisions in elections,
  • provide easy and quick access to voting on matters that user is interested in
  • reduce of information noise.

Lean Canvas

I used the Lean Canvas tool to create a UX strategy. It is a variation of the Business Model Canvas created for startups. Lean Canvas is more oriented towards fast creating the most effective solution.

An important measure of success will be, the number of active deputies in-app. The competitive advantage will come from the use of so-called "Plain language", which unfortunately involves additional costs of maintaining an editorial board.
Despite the non-profit structure, a potential source of income can be a request to make a donation. Application stakeholders can also try to apply for support Non-governmental organizations.

Completed Lean Canvas (in Polish)

Competitor Analysis

As part of the direct competition analysis, I researched: the website of the Sejm of the Republic of Poland, on-line parliamentary reports (websites of various Deputies). Indirect competition are mass media (online news services, but also press and television) and government websites of other countries (e.g.
It turned out that, apart from the form of application, the created product will be found on the "blue ocean" without any direct competition.

Competition features that should be avoided in the created application:

  • not showing information sources
  • no reference points for the topics
  • difficulty in finding a specific topic

Activities / Objects / Features

This method was used to describe the screens and interface elements needed to perform a specific task by the user. In the process of simplifying the access path to information, an idea emerged for the so-called "scoring" - a deputy rating calculated from the average of it's points. Working further with AOF method allowed me to observe the repetition of application key elements.

Red Routes

I used the Red Routes for each path and activity written in the Activities/Objects/Features. Red Routes made it possible to prioritize which functionalities are the most important for the user. Selected elements will be included in the MVP version, as well as in the first prototype and usability tests. Such selection will allow me to refine the key aspects and functionality.
Key features:
  • Search
  • Showing the voting results
  • Information on upcoming votes
  • Filtering using topics important to the user
  • "Scoring" – quick summary of the deputy's work
  • Percentage of election plan completion

User Flow

I used User Flows to write down the steps that the user will go through when performing specific tasks:
  • Checking how the deputy voted on the selected topic
  • Compare the activities of deputies
  • Assistance in choosing a candidate before the elections
The structure of the application turned out to be very complex in terms of information provided to the user on a single screen. At the same time, I tried to simplify and shorten each Flow as much as possible, so the user can quickly reach the selected information.


By combining User Flows and adding the missing screens, I wrote the application's Flowchart. One of the issues of the diagram was to select a path that will appear only before the elections. It is an added value that is very important for future users. Despite a large amount of information and data, the entire structure is not overly complicated. I have selected several screens that can be used as "templates" for other subpages.

Sejmoscope's Flowchart



Based on previous phases, I made an interactive prototype using Axure RP. In order to differentiate a large amount of text, I made a few distinctions by differential styling of the elements. It was caused by the way we consume texts placed on the screen. This way the prototype was more expanded than the typical low fidelity mockup.

Mobile prototype (screens in Polish)

Usability testing

For the test, I used a smartphone with a prototype (Axure Share). The aim of the study was to detect and correct usability errors and to check how users understand the information architecture.

During the tests, it turned out that the information architecture is logical and intuitive for users, although the methods of getting to the same information differed. Both Persona users and people with low political commitment were recruited for the tests. Therefore I could compare whether there were large differences in the way of use (e.g. due to the used vocabulary).

Prototype corrections after usability testing (screens in Polish)


  • The project received very positive feedback from the users, however, the declaration does not necessarily involve actual behavior later.
  • Strong exploratory research allowed me to create not only a product but also a business model or checking the potential directions of application future development.
  • The initial idea changed as a result of user interviews (IDIs) and observation of what kind of software they might need.
  • The competition analysis made it possible to confront the idea with the existing competition. This tool helped in creating a value that is not yet available on the market.
Adam Klimas
Adam Klimas
Get in touch