Why should you use ShiftX?
Most process tools are either extremely hard to use or an unstructured mess.
We create a process tool that can be used by anyone because you only achieve an accurate picture of your organization's processes by enabling everyone to take part in the modeling.
Collaborate with your colleagues to find out how you can improve the as-is processes and map the to-be processes at your workplace with ShiftX.
What can ShiftX do?
Some think of ShiftX as a place where they can map out their internal processes, identify who is supposed to do what when, and understand how workflows are connected throughout the workplace. Others use us more as a customer journey tool for mapping out important touchpoints, systems, actors, and issues. No matter how you use ShiftX, we create a single source of truth for all the processes that are important to you.
What can ShiftX do for you?
- A single source of truth for all workflows across sectors and departments
- A collaborative tool that makes it easy to facilitate workshops for internal processes, workflows, and customer journeys and document them at the same time
- Include everyone at work – anyone can use ShiftX, no certification or training needed
- Gain control of as-is scenarios to see how you can optimize to-be scenarios
While anyone can use ShiftX, the roles that have benefitted from this tool the most so far include:
- Business developers
- Digitalization and innovation executives
- HR and Business Process professionals
- Service designers
Servebolt made ShiftX their shared common language for visualisation of business processesRead use case ->
How ShiftX helps Inselo close sales faster with quicker client understandingRead use case ->
Why do we build ShiftX the way we do?
We build ShiftX to be a user-friendly process tool to help people create inclusive and efficient workplaces, where everyone shares the same truth about how things are done. We work continually to improve the tool, but some things will never change.
We believe in user-friendliness, for real. If you want to design and create something that is meant to be used by anyone, you have to test that it actually can be used and understood by anyone. We use Shipright to make it easy for our users to give us product feedback. In addition, we keep an open and accessible roadmap to stay transparent about what we are currently working on.
When making software, you always have to choose where to put it on the “Flexibility vs. Opinionated” scale. Should it be an open sandbox where our users can play around with total freedom and create whatever they want? Or should we create a more restricted space, and help our users by doing some of the heavy lifting “backstage”? For ShiftX, we have chosen the latter. In planning and mapping tools, full flexibility often leads to every team member creating their own structure and way of working - with the end result being pure chaos. We don’t want that.
Collaboration is key
In our opinion, if you want your process visualization and documentation to accurately mirror your reality, you have to let everyone participate in the mapping. That is why we strongly believe that a process tool should be so easy to use that any one of your colleagues can use it without needing extra training. We also believe that any workshops you run can be digital, self-documenting. With ShiftX, you can host and document a workshop simultaneously, so you won’t have to spend hours writing down what you all agreed on after the workshop is done. That’s real collaboration.
Everything is data
There are a lot of drawing tools out there. For example, some people use Microsoft Visio or Miro to draw a visualization of their processes and workflows. This probably does help them with documenting, showing and explaining the how and the who in their business processes. However, we believe the actual value of process mapping lies in the data, and that this value is lost if you use a “simple” drawing tool. All the actors, issues, and processes you map out in ShiftX are stored as data and are accessible throughout your workspace.
How ShiftX works
Using ShiftX is like writing a story about how your processes and workflows work right now, and how you want them to be in the future. But with ShiftX, you are not abandoned to write alone – all of your colleagues (ideally) chip in with their perspective. Together, you mold the single source of truth for your workflow by documenting your sales processes, onboarding processes, customer dialogues, and any other process you need.
As in real life, every flow (or process, if you like) has a beginning and an end. Between those two points, you can create as many:
- Steps (an activity, a task, or an event)
- Splits (splitting up the path into two or more paths)
- References (a subflow of your flow)
... as you like to best reflect your business process. These flows can be spread throughout your workplace, breaking down the barriers between departments, and closing the knowledge gap.
One step at a time
Steps are the activities, tasks and events that together make up your whole business or work process. These can be where the sales team books a meeting, a new employee meets her/his new boss, or any other type of event with touchpoints between humans and/or systems.
To get the most out of ShiftX as a tool for collaboration and shared understanding, use it to tell the story of your process or workflow through each step’s narrative field. This way, all your colleagues can be a part of your workplace’s shared story.
Control your issues
ShiftX enables you to visualize your real-life work and business processes. This includes all the issues that need further work – whether they are pain points or areas for improvement.
Mapping issues is key to getting the most out of ShiftX. Identifying all the issues in your, a colleague’s, or the team’s flows provides you with a good overview of what you need to do next. This will also help you discover any potential issues in the future, and make cooperating with your colleagues a lot easier.
Versions – a history of processes
When publishing a flow in ShiftX, you create a version of that flow. You can later alter the version, and when you republish it, you suddenly have two versions of the same flow. It’s just like magic!
Well, not quite magic, but you will probably find that it comes in handy if, for example, you want to look back at how you did onboarding, reporting or [insert one of your other flows] in 2019.