Hi, I’m Adam
I’ll be your guide and will do my best to make your time worth here.
I need ~4 minutes of your time.
I would offer you a cup of coffee or tea but in those circumstances, you know…
Just relax and swipe away!
What we do
We design User Experience of digital products.
Our projects are WCAG compliant and on par with each platform navigational guidelines.
Our design is not flashy, we don't do it so it looks nice on Dribbble. It has to work and solve problems you pay us to solve. It has to work for years.
We treat brand visual identity seriously. We don't just take 2 main colours and go nuts with everything else.
I’ll focus on a different aspect of our work—the deliverables. Think style guides, UI patterns libraries, and prototypes. If you’re familiar with Atomic Design, that’s what we do + prototyping on top of that.
Let me explain what’s that about.
Why Design Systems
When the job is to design 600 pixel perfect screens, simple screen–by–screen workflow won’t cut it.
In projects like this, there are dozens or more developers and other designers involved. The job then is to design components that will be reused. Those components have different states. Think empty state, 1 item, few items, too many items, error, warning.
With this approach—a design system becomes a living documentation.
Why we prototype
To be sure that our (by us I mean you and us) vision of the product will work, we create prototypes.
We build them with components from design system. We test them with people. We consider the feedback, make changes and test again.
It’s much more than few static screens connected in InVision, Marvel or Axure. Those are working apps and websites. They are mocked with real data and ready for real world scenarios.
Managing change is the biggest problem in big design projects.
It may not be obvious at first but think about it.
You manage a 600+ hi–fi screens project, you have a new idea, a great one. To implement it, 120 of those screens need to be changed, manually! Someone has to open those files, make the change, update InVision, Marvel, Axure etc.
“Who pays for that?”, “How does it affect the timeline?”, “Will it work in all contexts?”.
What usually happens?
That’s right, you guessed it: NOTHING! Everyone knows how painful it’d be and usually doesn’t even try. Sometimes, a few key screens get changed and it introduces a giant mess for everyone.
We hate that, we’re crazy about efficiency and that’s was painful that we would fear to make changes.
We have all the great tools that software development offers. We use version control, we separate data from layout and reuse layouts. We can use responsive styling libraries for web and mobile.
It all gives a confidence that changes can be made quickly, can be tested easily and won’t break anything.
Product development perspective
Most tools for UX “prototyping”, available now, are just static images moving on the screen.
The result is not true to the end experience, not true to the platform of the product (be it web or mobile).
How do you show animations and inertia or those subtle changes for input? Tools like Framer or Origami work well for prototyping isolated interactions/transitions. They don’t solve the problem of showing them on 600 screens with variations.
Working with developers
We have the pleasure to work with outstanding developers. We highly respect their work. It’s natural that they are not UX designers, they are developers. Usually, the project files they get from designers lack around half of the context needed.
Then, usually one of those 2 scenarios happen:
They will ask about every little thing. Spacing, animations timing, interaction states, etc. Better for quality but very time–consuming. Another side–effect is that most of those answers aren’t well–thought. They are rather figured out on spot.
They will do things the way they think is OK. Obviously worse—unless you work with some UX–gifted developers. Usually the result is not what we aim for, to put it nicely.
Technology we’re using for prototyping
We build tools on top of technologies like React, Polymer, Tachyons, Firebase, GraphQL. We have years of experience solving that kind of problems so we know how to use them efficiently. What we deliver works on the native platform of the (soon to be) product—mobile, tablet, web.
Developers can use their tools to check every implementation detail. Like spacing, colours, dimensions, animations timing. We also ship a Storybook that showcases all components in all their states.
Testable, real data
We use real data, we scrape it from real sources if possible. We do it so we see edge cases for real–world scenarios. We can swap or have different sets of data for tests with real users, in believable conditions. Something that relates to them directly.
Here’s a story: One of our projects was location based. When we knew exactly where we would test with people.
We put stuff on map nearby the test location. People were sure it’s real data in a live app.
This leaves no room for misunderstandings or cognitive fatigue. Try testing a map app (zooming, panning, selecting) on linked static screens.
We believe life is too short to waste it on doing dumb things. That’s why we use Scrum to run our projects.
If we (and by we I mean you and us) are wrong with any assumptions, we want to know that ASAP and react accordingly.
First, we deliver Minimal Viable Product—we pick crucial functions and do them first. Then, we test them. When we know what works and what doesn’t—we move forward with next features.
In more details
You don’t know everything from day one. You assume plenty and think you know. It’s not just you, it’s us all, humans.
That bold plan, those beautifully aligned Gantt charts. They quickly become irrelevant when you confront them with what you learn during the process of creation.
Sticking to them isn’t very smart. That’s why we don’t want to be forced to. We don’t want our clients to be. That’s what fixed priced contracts enforce and it’s not good for anyone involved.
In the world of digital products, swift and agile is way better than slow and „waterfall”.
In very down to earth terms
- We need to understand the idea and business model
- We work internally for a while (about 3-5 days)
- We come back with a tangible concept for a workshop together
- When we’re on the same page, we work on the visual design
- When we agree, we build a prototype
- We iterate visual design and overall UX on the prototype in one–week sprints
- When the concept feels right, we start to include users in iterations (~2–3 weeks from start)
- First version (or MVP) is ready for development and getting feedback from real users
- We start iterating on next features and the process continues
NGO.pl is the biggest non–governmental portal in Polish internet. It’s 16 years old (think about what you were doing in 2001). More than 1 million people visit every year. It serves a great purpose in NGOs community in Poland.
We’re responsible for the whole redesign. We work together to introduce smart and viable monetization options.
We deliver fully working prototypes with scraped real data. Those have a with new Information Architecture, new navigation, new visual design. They are fully responsive. On top of that, there is a full design system.
This project is ongoing and is estimated to end at the beginning of 2018.
Orange has a total of ~16 million customers in Poland. They’re the biggest mobile and landline operator here.
It’s a client we’ve done biggest projects with. We work with them on:
Web, mobile & tablet applications (Mój Orange). Full technical and UX analysis. We created a new information architecture, new navigation, new graphical design. RWD prototype. We helped to redesign the whole process from the ground up. It was a huge project. Overall more than a year of work, more than 600 hi–fi screens created in this project alone.
Login and registration cycle
Web, mobile, omnichannel process redesign. Big in terms of service design. Think about security implications, legacy considerations in a company like this. More than 30 workshops with different departments had a place. RWD prototype delivered with documentation.
Online knowledge base
The challenge was to create a more efficient KB and combine client facing and internal ones. We actually analyzed (read!) Orange’s existing knowledge base to create information architecture map and content inventory. From that, we came up with more natural and understandable information architecture. Based on that we delivered a working RWD prototype. We also designed a sophisticated search system.
Web sales process audit and recommendations
Selling contracts with mobile handsets isn’t easy. We audited the existing path. Recommended changes and created flows for discovery and conversion paths. We delivered a report with recommendations. Based on that, a small prototype showing IA and micro interactions and transitions.
There were few more I won’t cover in details: in example, we worked with their CSR on a system for utilizing old phones.
mBank Corporate Banking
mBank’s tagline is “Mobility Icon”. They’re considered the #1 in mobile and online services among Polish banks. You should know, that banking systems and services in Poland are considered as one of the most modern and sophisticated in the world.
We started with UX audit for their new mobile and tablet applications. Then we were asked to help with the design for those. We delivered designs for mobile and tablet applications. W also helped with quality assurance during the project.
It was an interesting project with tight time constraints. It all happened in 3 months. Keep in minds in a corporate banking app—it’s much more complex than B2C with lots of extra features.
RR Donnelley Poland
RRD is a Fortune 500 company founded 150 years ago in Chicago.
All project done together are under a really strict NDA here. We help this giant with digital product development for their giant clients.
LivaNova is a global medical device manufacturer. They develop devices used for cardiac surgery, neuromodulation and cardiac rhythm management.
We’ve made a sales force iPad app together. By that I mean: content, navigation, information architecture, visual design.
We started this project by receiving training about heart diseases and how pacemakers work. All that, so we could come up with something smart and specific. We think we did.
innogy Innovation Hub
innogy Innovation Hub is an acceleration programme for startups. It’s founded by innogy (named RWE before, the energy giant).
We had 6 weeks to create and test an assumption about a new technology. One that would help you find parking spaces in crowded cities.
We worked together on the functional scope of the app, created a prototype and tested it with people.
The prototype was build in a way, that testers were convinced that they see real data. The project took 4 weeks from 6 weeks limit.
Date for Date
This was fun! We created a new mobile dating service for the Swedish market. From scratch. The only thing given was the name.
Together with the Product Owner Glen, we figured out a new approach to dating. One that wouldn’t treat women as “objects”. That wouldn’t have that “meat market” vibe to it.
We conceived, designed and actually coded the app in less than 3 months from scratch. One of the most interesting projects of our lives.
Pracuj.pl is the biggest job posting site in Poland and this part of Europe. Think Polish monster.com.
We designed and coded mobile and tablet applications (iOS and Android).
Rating went from ~3 to ~4.8 stars in stores.
Funny thing—our design was all flat and it was the time when iOS 6 hit the shelves and iOS was still skeuomorphic (think wood and leather).
Think about Gastronauci as Polish yelp. The service was highly respected and widely used.
We designed and coded iOS and Android apps (they had web only).
It was a big success. Gastronauci got acquired by “Zomato”.
We’ve done many more projects.
From prototyping an app for citizens to inform authorities what to fix in the city. It was done during a 48h hackathon in Stockholm.
To helping a startup from Silicon Valley to improve UX in their multi–platform, in–game leaderboard.
Bragging is tiring, let’s talk about…
So, how much for the pleasure
All this for only 59,99 EUR/hour!
Not the most formal company website you’ve seen in your life, right?
Seriously, we work for 60 EUR/hour. It’s for an actual hour of work. No lunch, no coffee breaks, no man–days—just work charged.
“But we need an estimate”
Estimates are hard in software projects (not only here).
I’ll try to break it down into something tangible.
We usually need about 4 weeks to deliver the first MVP. Analyzed, designed and prototyped.
From that point, the development can start and we can work on next iteration.
Those 4 weeks translate to around 9.000–11.000 EUR (2 people working about 5 hours a day). We can make it fixed price but it’ll take time to set the scope, the agreement and we’ll have to really sit down on the estimate. We all have to understand that it’s the cost of the scope written in the agreement. If find that it doesn’t make sense, we need to alter the agreement.
We’ll also have to add some margin for the risk that we underestimated the project. It’s always better to go with Time & Materials, for everyone.
That’s all, thanks
Think about it for a second.
You just read a business proposal that says about lots of technical aspects of how projects are done. You would expect it to be very formal and boring. I would.
If I did a good job, you should “have a feeling” about us (or me) at this point.
You may think it’s unconventional but I hope I’ve made you feel that you can trust us in the experience and engagement field.
Of course, I’m not sure if you actually read it all. I hope you did because it describes everything you need to know about who we are and how we do things. Or so I hope.