Week Zero – Why is it Necessary?

Do you have a new idea for your business or industry? At Bitsapphire, we can help bring that idea to life. The first step is determining the validity of your idea.

In order to decide if an idea is viable, we must identify the problem, solution, and the need/demand for said solution. Bitsapphire will work with you to break down and analyze your idea. This will allow all of us to better understand your idea’s potential and its real world functionality. Ideas rarely translate flawlessly from conception to prototype. Our onboarding process will help us recognize inconsistencies and prospective changes early on in our working relationship.

Here at Bitsapphire, we have named this process “Week Zero”.

During the “Week Zero” process you will work closely with our team to evaluate every aspect of your idea, especially from a potential users’ point of view. Bitsapphire has all of the necessary tools and assets to flush out your idea and bring it to life. While this process is called “Week Zero” since it is the beginning of our working relationship, the entire process usually takes 4 weeks. Of course, every idea is different and each “Week Zero” process is going to vary somewhat depending on the nature of the problem and solution.

Here is an outline of what you can expect during each part of “Week Zero”:

Week 1

Day 1:

You and your team will meet with Bitsapphire via Skype. You will present your idea as well as any relevant background information. How did you conceive this idea? What problem does your idea solve? Each detail will help us understand the scope of your ambitions.

From here, we will ask your team to provide us with a list of potential users that we can interview. These potential users or stakeholders will serve as a sample group of your target users. These should be people who will benefit from your idea and would want to use your solution. These stakeholders should have real world incentive to use your proposed solution. We usually ask that each member of your team provide 1-5 stakeholders. This process is repeated 3-4 times until an adequate list of potential users is compiled.

Day 2:

Stakeholders are then individually interviewed regarding the idea. These interviews will help us grasp the problem from a potential users’ perspective. In most cases, these interviews illuminate a number of issues, needed changes, or inconsistencies that were previously overlooked. It is also common for these sessions to reveal further problems that can be solved and solutions that can be implemented.

Day 3:

We continue interviewing potential users and gathering data. Four stakeholders are interviewed per day.

Day 4:

Your team will meet with Bitsapphire to discuss and analyze the data that has been collected thus far.

Day 5:

The last group of stakeholders are interviewed and all of the results are compiled. This data is used to create a few “user personas” based on the stakeholders characteristics and pain points. While keeping these “user personas” in mind, our user experience team will begin creating an outline and flow diagram for implementing your idea. We will then design a wireframe for the best possible user experience that will be tested by the stakeholders during week two. Everything is designed with the stakeholder in mind.

Week 2

Once we have a clear idea of your targeted user and a general wireframe, the next step is exposing your stakeholders to a low fi prototype. This prototype allows everyone to see a visual representation of the idea. One of the main purposes of lo-fi prototyping is to focus more on the conceptual aspect and explore related alternatives before deciding on a definite design. Stakeholders will be shown the low fi prototype and their reactions and behaviors will be recorded. Feedback is received and revisions are made to the low fi prototype each day during week two.

Week 3

Using all of the feedback we have gathered during week two, we upgrade to a high fidelity prototype. While a low fidelity prototype allows us to see a visual representation, a high fidelity prototype will have a varying degree of functionality and usability. Stakeholders will continue to be interviewed.

Week 4

The high fidelity prototype is updated using data collected during week three. A final round of interviews is conducted with your team as well as stakeholders.

End Result

By the end of the “Week Zero” process you will have a much clearer understanding of the real problem that your idea is based on. All of the research and stakeholder interviews we conduct will provide you with the right solution for that problem. Your idea won’t just be an idea anymore.

We will provide you with all of the relevant collected data, notes, interviews, stakeholder information, user personas and labels, and prototypes. It is important to note that some projects may warrant a detailed white paper instead of any prototype models. An example of such a scenario would be a detailed protocol white paper.

Additionally, the “Week Zero” process establishes trust and communication between you and Bitsapphire immediately. Moving forward, we can provide a detailed time and cost development proposal for future steps.