5min read

How to prep an effective kick-off workshop

We look at projects holistically. As designers and engineers, we aim not to simply be contractors who execute somebody else’s blueprints, but to help our clients build their tech cathedrals. This means understanding the product we are building down to its very roots and details. To achieve this, we kick projects off with a (preferably) face-to-face client workshop.

What are client workshops for?

Firstly, they help everyone get on the same page, quickly. As a designer, project manager or engineer, you might’ve gotten a description or summary of the project, or maybe you got a 60-page-long description of why it is amazing. That’s great, and you will need all those things (more on that later). But all materials are useless if you understand them differently than your client. This is why understanding goals and vision is crucial in order not to waste valuable development time.

Secondly, a workshop is a great tool to coax ALL information out of a client. Maybe they know stuff they’re not sure enough about to write down, or they didn’t deem important. Thanks to a couple of tricks described below we can make sure that we have everything we need to start working.

Finally, it’s a fantastic kick-off. Ideally, everyone meets face-to-face. For us, this includes all the stakeholders client-side and both designers and developers on our side. It’s a lot more fun to work on a team you know and to collaborate with people you can put a face on. By gathering everyone you also make sure you get everyone on board with your project. It’s a lot harder to be a naysayer when you co-create something.

Client workshops are not science. We don’t have rigorous procedures or must-have exercises. But we do have a framework we use to determine how to setup and run a workshop which I will present to you in 3 simple steps.

Step 1 – Check what you have

We use a list of four bases to check how much information we have about a new project. They are:

Four bases


What problem are we solving? Why are we doing this project? What are its goals? These are key questions for a product’s success. You can, of course, build one without knowing any of the answers, but you wouldn’t walk into a dark basement without a flashlight, hoping there were stairs, would you?


Finding out as much as you can about future users of the product can be very helpful for prioritising work and ensuring you are building an app that people will want to use. If you are building a product for an existing brand or platform, you should be able to obtain real data about current users. If you are starting from square 1, it might help to think about existing products the target audience would be using right now, e.g. if you are targeting runners, maybe there is data about Nike+ users you can use.


A hot topic in IT projects. How big is this thing gonna be? Is there a feature list, or a description of what the product is going to contain? Gather data as specific as possible, as scope will help you build a realistic timeline and estimate well, which in turn is going to help you avoid heated discussions with the client.


Whether you work with a big corporation or a budding startup, the product you’re building will have a brand. If you are just building software, it’s probably not your responsibility to think about the actual branding, but it helps to know as much as possible, as it might influence priorities, e.g. is it more important that the interface has fancy custom animations or that the data fetching is as performant as possible? For designers, this is key to designing the UI.

Step 2 – Get what you need

After you have determined what information you can get upfront, you will need to get the rest. Sometimes you will have a lot of time to prepare, sometimes it’s all last minute. We have some tried and tested ways for both scenarios.


If you have one week and the client has no clue about story, ask them to fill out a Lean Canvas. It is a tool designed to cover all of the key questions of a project. You can find out details about the reasoning behind it here.

If you only have a day, it might be too big of a task. Instead, we use a short exercise we call Fill The Gaps invented by our Head of Design, Karolina:

Try out [product]! You will never [user problem] again. Thanks to [most important feature] you will be able to [goals to achieve]. Feel like [user’s emotions].

By writing a corny advertising slogan, the client will be forced to think about the bigger picture and the end user.


A lack of data about users is almost exclusively a problem with new brands, where there is no existing user base. If you are working with a bigger company, they will probably already have personas or actual statistics you can ask to see.

If you have a week and no data about potential users, you can ask your client to do a simple survey with people who match their dream user profile. These will include some universal questions (how familiar are they with technology, what are their favourite apps, what are their favourite brands, their typical day) and some questions pertaining to the subject matter. For a shopping app this could be how often they shop for new clothes and where, for a job board this could be how they got their last jobs. Make sure questions are simple and easy to interpret.

If you only have a day, give your client a list of key user characteristics to think about: age, lifestyle, job type/level, where they live and what brands they would currently be loyal to and other things important for your area.


If your client has no idea about scope, do nothing. You should work out a smart feature set and divide it into milestones together after you have finished the workshop.


If the brand doesn’t exist, do one thing regardless of how much time you have: ask the client for 5 adjectives that they would describe the product with – the brand personality. An example brand could be youthful, energetic, happy, positive, simple.

If you have more than a day: most clients are not designers, so they might have a hard time naming what they want. This is why we work with examples: in the workshop we show them various app screens and they say like or dislike. We also prepare examples of visual trends (e.g. flat and colourful, gloomy gradients, white and light) and show them as directions we can go in, based on the 5 words they provided. Prepare them before the workshop.

Visual directions

Step 3 – See what you can do

Now is the time to plan. We share our favourite tools in part two of this post – read it here!


MagdaUI Designer


Sign in and expect sharp insights, recommendations, ebooks and fascinating project stories delivered to your inbox

The controller of the personal data that you are about to provide in the above form will be Polidea sp. z o.o. with its registered office in Warsaw at ul. Przeskok 2, 00-032 Warsaw, KRS number: 0000330954, tel.: 0048 795 536 436, email: (“Polidea”). We will process your personal data based on our legitimate interest and/or your consent. Providing your personal data is not obligatory, but necessary for Polidea to respond to you in relation to your question and/or request. If you gave us consent to call you on the telephone, you may revoke the consent at any time by contacting Polidea via telephone or email. You can find detailed information about the processing of your personal data in relation to the above contact form, including your rights relating to the processing, HERE.

Data controller:

The controller of your personal data is Polidea sp. z o.o. with its registered office in Warsaw at ul. Przeskok 2, 00-032 Warsaw, KRS number: 0000330954, tel.: [0048795536436], email: [] (“Polidea”)

Purpose and legal bases for processing:


Used abbreviations:

GDPR – Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016
on the protection of natural persons with regard to the processing of personal data and on the free movement
of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)

ARES – Polish Act on Rendering Electronic Services dated 18 July 2002

TL – Polish Telecommunications Law dated 16 July 2004

1)        sending to the given email address a newsletter including information on Polidea’s new projects, products, services, organised events and/or general insights from the mobile app business world |art. 6.1 a) GDPR, art. 10.2 ARES and art. 172.1 TL (upon your consent)

Personal data:name, email address

2)       statistical, analytical and reporting purposes |art. 6. 1 f) GDPR (based on legitimate interests pursued by Polidea, consisting in analysing the way our services are used and adjusting them to our clients’ needs, as well as developing new services)

Personal data:name, email address

Withdrawal of consent:

You may withdraw your consent to process your personal data at any time.

Withdrawal of the consent is possible solely in the scope of processing performed based on the consent. Polidea is authorised to process your personal data after you withdraw your consent if it has another legal basis for the processing, for the purposes covered by that legal basis.

Categories of recipients:

Your personal data may be shared with:

1)       authorised employees and/or contractors of Polidea

2)       persons or entities providing particular services to Polidea (accounting, legal, IT, marketing and advertising services) – in the scope required for those persons or entities to provide those services to Polidea


Retention period:

1)       For the purpose of sending newsletter to the given email address – for as long as the relevant consent is not withdrawn

2)       For statistical, analytical and reporting purposes – for as long as the relevant consent is not withdrawn

Your rights:


Used abbreviation:

GDPR – Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016
on the protection of natural persons with regard to the processing of personal data and on the free movement
of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)

According to GDPR, you have the following rights relating to the processing of your personal data, exercised by contacting Polidea via [e-mail, phone].

1)       to access to your personal data (art. 15 GDPR) by requesting sharing and/or sending a copy of all your personal data processed by Polidea

2)       to request rectification of inaccurate personal data
(art. 16 GDPR) by indicating the data requiring rectification

3)       to request erasure of your persona data (art. 17 GDPR); Polidea has the rights to refuse erasing the personal data in specific circumstances provided by law

4)       to request restriction of processing of your personal data (art. 18 GDPR) by indicating the data which should be restricted

5)       to move your personal data (art. 20 GDPR) by requesting preparation and transfer by Polidea of the personal data that you provided to Polidea to you or another controller in a structured, commonly used machine-readable format

6)       to object to processing your personal data conducted based on art. 6.1 e) or f) GDPR, on grounds relating to your particular situation (art. 21 GDPR)

7)       to lodge a complaint with a supervisory authority,
in particular in the EU member state of your habitual residence, place of work or place of the alleged infringement if you consider that the processing
of personal data relating to you infringes the GDPR
(art. 77.1 GDPR)

No obligation to provide data:

Providing your personal data is not obligatory, but necessary for Polidea to provide you the newsletter service

Refusal to provide the above data will result in inability to receive the newsletter service.


In the process of providing the newsletter service, we make decisions in an automated way, including profiling, based on the data you provide.


“Profiling” means automated processing of personal data consisting of the use of your personal data to evaluate certain personal aspects relating to you, in particular to analyze or predict aspects concerning your personal preferences and interests.


The automated decisions are taken based on the analysis of clicked and viewed content. They affect the targeting of specific newsletter content to selected users registered to receive the newsletter service, based on the anticipated interests of the recipient.