November 29, 2018
Working with an outsourced team can be a challenge. Different locations and time zones, sometimes even different cultures. You are where the business is, working hard to move things forward, while your hired team is elsewhere, building something that will hopefully one day become your product.
How can you make sure that your vision is reflected properly in the finished product? How to best lay the foundation for a productive transfer of knowledge between yourself and the team?
We always suggest—insist even—that our clients take part in discovery workshops, because we believe that the way you start your journey influences what happens later.
The Discovery Workshop is meant to unravel the truth about your business and its needs. We are not experts in your particular field—you are. And you will be our gateway to your business.
After conducting many such workshops myself, I know that getting to know each other as people and achieving alignment together ensures smooth cooperation in the future.
Yes, it is possible to conduct such workshops purely online and we’ve done that in the past but it led to so many instances of miscommunication later that I must say that the juice wasn’t worth the squeeze.
In this article, I will outline how we organize the Discovery Workshop at Monterail, what you can expect to get out of them, how to prepare, and why you shouldn’t skip them.
Well, let’s dive in.
The journey begins the moment you contact us. One of our Account Managers takes you under their care, sets up relevant calls, listens closely to get to know your ideas, needs and requirements. This part varies greatly, as your specification can be written down in four forty-pages-long PDFs or one, highly condensed email (both real-life examples from our past).
Then, we enter the discovery phase.
The first part is called the initial scoping session. Based on our experience, the provided specification, and some quick research, we provide you with a ballpark estimation. This estimation is not completely accurate and can’t be so. You say: “I want a car,” and tell us the color and all the other details, and we then tell you that its cost can vary from X to Y. Then, based on the style of our communication, types of questions we ask, and the price range we offered, you decide whether you want to proceed with us.
But to close the deal we need something more detailed.
In order to validate your business ideas, we need to understand your objectives and have real interactions—we use the Discovery Workshops for that.
That’s when you and our team (designer, developer, business analyst, and project manager) meet for two days to achieve something, and the outcomes of it is crucial:
During those two days, we try to unveil the truth about your idea and then start building the documentation.
To do the former, we are in constant inquiry mode and ask a lot of questions. Some may seem boring to you, but they’re really important to us. Some will be tough, but necessary, and it's easier to ask them face to face. There is much less space for miscommunication in a conference room than in the email threads. Instead, it brings focus and sense of importance and urgency (two-day timeframe).
Sometimes a workshop is just a compilation of necessary questions asked in particular moments and in a particular order.
The outcome is hopefully the following—we establish what your users’ problems are and how to solve them with your product.
Now, we need to address the latter: common understanding of groundwork for constant validation of business goals, user needs, and technical feasibility.
The answers to the above-mentioned questions and a sense of mutual understanding between you and your team is nothing without proper follow-up. Up to this point, we managed to establish what our destination is. Now, we need to map out the road that will get us there. We need a good documentation.
For that, we do a mash-up of sitemaps, user flows, user stories, and clickable prototypes. We don't do static wireframes or designs, because there is always movement in interface design. Always an origin and a destination. It's important to capture the journey, not the design of a particular screen.
The workshop gives us the unprecedented ability to visualize the whole system on a wall or a whiteboard. We get a few hours to document all the steps of the user and accompanying system actions and see them as a whole, looking for problematic areas and reacting.
We start the documentation during the workshop, but finish it in about a week after and send it to you with revised and detailed estimates.
Here’s what you gain by participating in the workshop:
The idea of the Discovery Workshop is not only about the design, development or the process itself. It’s about embracing the human side of business and software development. In order to fulfill our mission, we create a relationship with our client and strive to deliver something true and authentic. This personal connection is crucial as people look for cultural fit with who they do business with. We always make sure to remember that.
See what else impacts the final design of your product:
Unravel the truth about YOUR business
During a 2-day Discovery Workshop, we'll discuss topics from design to choosing the tech stack and establishing the final project scope. Bounce your ideas off the Monterail team and make sure that your vision becomes reality.