01.

Why?

To validate a concept before we proceed with development, we recommend a ‘5 day innovation sprint’. The innovation sprint enables us to build and test the idea that you have in one week. After the week we will have a better understanding of how to execute your idea, and you will know whether or not the idea creates value for your users and your business.

This knowledge will enable you to take the next decision about what to do next. At this time, the reporting and prototype may be shared within your organisation so others stakeholders can easily get an overview of the process you have been through and the final outcome.

02.

Day 01

Before day 1 the client and us have prepared by mapping goals, strategy, analyzing competitors, user demands etc.

Method:

  • Define business goals and success criteria
  • Map challenges, ideas, solutions and thoughts
  • Ask the ‘experts’
  • Recruit 3-5 users that we will use to test the prototype

Output:

A prioritized overview of the challenges and possible solutions that have been challenged by experts and stakeholders

03.

Day 02

On day 2 we draft the ideas that we came up with on day 1. This will be done separately.

Method:

  • Draft the different solutions with the use of prototyping methods
  • Map user flow and make a storyboard for chosen concepts

Output:

  • Detailed Draft
  • Story Board
  • Mind Map
  • User Flow
04.

Day 03

On Day 3 we decide which ideas and what elements of the others ideas we want to test with the prototype. We will weigh and vote on the different ideas and look for potential conflicts.

Method:

  • Vote with the use of methods like ‘supervote’ and ‘strawpoll’ to ensure that all stakeholders are heard
  • Create a storyboard for the chosen solutions so that we are aligned on what’s included

Output:

A single prioritized and challenged concept that we will continue with

05.

Day 04

A designer and UX advisor will design a prototype based on the scope that we have agreed upon. The prototype will be clickable and able to show the concept to the users and other possible stakeholders.

Method:

  • Design a prototype
  • Make it clickable in Invision so that the users can interact with the prototype like a real app

Output:

  • Concept design on the chosen solution
  • A clickable prototype to be used for user testing
06.

Day 05

Day 5 will be used for testing with the respondents who we recruited on Day 1. The respondents are interviewed with one interviewer. It will be recorded and displayed on a monitor in an adjoining meeting room where the team is ready for feedback. Afterwards, we will evaluate and adjust accordingly and now have thorough material for the final decisions in terms of continuing the project or not.

Method:

  • User testing with representative users of the system
  • Evaluating and implementing feedback
  • Recap of the process and project, and clarification of the next step

Output:

  • User testing report
  • Decision proposal, validating the business case, roadmap and overview of the following process
01.

Why?

Software is an IT platform, which can live in almost all parts of your organisation, thus creating an urgent need for governance of all parts of the process. Too often we see companies with apps in three different frameworks, various push providers, no plan for their analytics tracking, and no shared server solutions across projects.

With the responsibility of your company’s IT setup, you want to keep things aligned, minimize complexity in legacy projects, minimize technical risk (e.g 3rd party providers) and make sure you have the resources available when need arises.

Our developer’s IT Governance will provide you with clear directions and policies, and help you make the right choices based on your current IT setup. We will also help you govern how applications are conducted across your organisation.

02.

Kick-off Workshop

First stage is about understanding the business and environment (external/internal) to reveal the potential opportunities, and we would typically touch upon the following topics and areas:

  • Enterprise vs. Consumer
  • Business critical factors/Pains – Stakeholders/Processes
  • Technology – Budget/Resources

This stage includes a combination of interviews, workshops, best practice and prior experience.

03.

Interviews and Desk Research

Second stage is about defining the opportunities, process and vision from a user and technology perspective. It is crucial that the solution is shaping the business and not the other way around. The stage revolves around the following topics and areas:

    • Goal/success criteria
    • Ideation/Opportunities
    • Target groups/Enterprise & Customer value
    • IoT/connected products/connected devices & mobility
    • Vision/user experience

This stage includes a combination of interviews, workshops, best practice and research and surveys.

04.

Governance Report

Third and final stage is where most organizations fail because they see a mobility project as finished when an app is launched, instead of seeing it as a crucial part of shaping the future for the organization. Based on the first 2 stages, we now start transforming the obtained information into tangible steps that makes us able to answer questions like Where? What? Why? When?

This provides you with a prioritized roadmap that shows you our recommendations and strategy for mobility services solutions.

01.

Why?

Software is an IT platform, which can live in almost all parts of your organisation, thus creating an urgent need for governance of all parts of the process. Too often we see companies with apps in three different frameworks, various push providers, no plan for their analytics tracking, and no shared server solutions across projects.

With the responsibility of your company’s IT setup, you want to keep things aligned, minimize complexity in legacy projects, minimize technical risk (e.g 3rd party providers) and make sure you have the resources available when need arises.

Our developer’s IT Governance will provide you with clear directions and policies, and help you make the right choices based on your current IT setup. We will also help you govern how applications are conducted across your organisation.

02.

Kick-off Workshop

First stage is about understanding the business and environment (external/internal) to reveal the potential opportunities, and we would typically touch upon the following topics and areas:

    • Enterprise vs. Consumer

<li?Business critical factors/Pains – Stakeholders/Processes

  • Technology – Budget/Resources

This stage includes a combination of interviews, workshops, best practice and prior experience.

03.

Interviews and Desk Research

Second stage is about defining the opportunities, process and vision from a user and technology perspective. It is crucial that the solution is shaping the business and not the other way around. The stage revolves around the following topics and areas:

  • Goal/success criteria
  • Ideation/Opportunities
  • Target groups/Enterprise & Customer value
  • IoT/connected products/connected devices & mobility
  • Vision/user experience

This stage includes a combination of interviews, workshops, best practice and research and surveys.

04.

Governance Report

Third and final stage is where most organizations fail because they see a mobility project as finished when an app is launched, instead of seeing it as a crucial part of shaping the future for the organization. Based on the first 2 stages, we now start transforming the obtained information into tangible steps that makes us able to answer questions like Where? What? Why? When?

This provides you with a prioritized roadmap that shows you our recommendations and strategy for mobility services solutions.

Let’s Work Together

Have a project in mind? We’d love to hear about it. Let’s create something great together!

Let's Connect!

Use the form below, or send us an email

    Let’s Talk






      By submitting your message, you agree to the SoftwareCo Terms & Conditions