Skore, along with Duena Blomstrom, Co Founder and CEO of People Not Tech, were honoured to be invited on to Cloudbusting, an insightful podcast from Cloudreach, hosted by Jeremy King and Dave Chapman. Jeremy and Dave are Thought Leaders in Cloud Computing. Together, they explore what it means for organisations and their business models when they move to the cloud. Their approach is to view cloud migration from a holistic point of view, including the impact on employees and customers.
Skore’s Chris Green, Partner Director and Craig Willis, Customer Success Director joined them last month. They discussed the importance of a human focused approach to process mapping and outlined the impact of Robotic Process Automation.
Process mapping is an essential part of any change or transformation and cloud migration is no different. Process discovery allows organisations to re-evaluate their core processes and ensure they are the right ways of working for the modern world. This is an essential step in any cloud migration process.
Have a listen.
Listen to the podcast here to learn more about how Skore brings a human approach to process discovery and makes it easier to engage with everyone, not just the technical experts in your organisation. Craig and Chris outline Skore’s approach and how it can revolutionise the change management experience for any organisation.
Skore is committed to improving the user and therefore human experience of digital transformation. We are proud of the positive impact our platform can have an organisation. Find out more here:
Skore is the Process Discovery, Insights and Improvements Software platform that enables you to map processes live at the speed of conversation. Our solution provides valuable, instant insights and focuses on driving engagement and collaboration within an organisation.
Following the success of the last training sessions, Skore is pleased to announce another date in 2019 to meet with increasing demand.
The training is designed for Business Analysts, Consultants and Change Management professionals using Skore to map and analyse processes. The one day Digital Discovery training will enable participants to get up to speed running live capture workshops and generating insights using Skore.
At the end of the training, participants will be eligible to apply for the Skore Practitioner Certification.
The next session will be held on the 3rd December 2019 at the Portsmouth Technopole, Portsmouth.
If you’d like to learn more about the Skore training and accreditation program please get in touch by emailing firstname.lastname@example.org for more information.
Congratulations on getting your Skore Workspace! Your process discovery experiences are about to become collaborative, enjoyable and satisfying. In this article we’d like to show you how to capture a process in Skore and explain why it is so effective.
For this exercise we are using the aircraft turnaround process as an example as it demonstrates the many different aspects of process visualisation and is a pretty complex process.
The basic components of a process
Processes are a series of activities that transform inputs into outputs. At the core we need to know what happens, who does and why. Skore is built around these core questions.
Drawing a process with Skore means adding a What box to describe what happens and who does it, then a Why box to describe the output of each step in the process.
Click on each box to edit text and describe the activity, the role that does the activity and the output of that activity.
Let’s use a simple activity: Unload Passengers
In this example the person responsible for safely unloading the passengers is the Cabin Manager. The reason we unload the passengers… well apart from the fact they want to reach their destination… we need to get them off as quickly as possible so we can start preparing the cabin for the next flight.
You can read it like a story:
As a Cabin Manager I need to unload passengers so that the cabin can be inspected and cleaned.
Drawing process flows
Now we know how to define a single activity in a process let’s look at how to create process flows. If you feel really confident you can start capturing activities in a flow. However here we recommend an easier way to get started and make sense of business processes.
Your audience will always find it easier to tell you what they do rather than why they do it. In fact asking someone directly why they do something can make people feel uncomfortable.
So let’s start with some basics. First off we want to clearly show what process we’re mapping. Make sure you have the title of the process clearly visible.
Next let’s set the ‘scope’ of the process. This means where the process starts and where it finishes. The first input and the final output.
Now we know what we’re looking at, the next step is to try to capture the main activities. So start putting a few what boxes onto the page and then ask what the main tasks are.
That wasn’t so hard and we didn’t upset anyone yet. Rearrange so all activities are in the right order. So now try to add the role of the person who owns this piece of work.
The next stage is to add the outputs. Each output becomes the input for the next activity so think of them as the handover from one to the next. What tells you one activity has finished and the next is ready to start.
This could be as easy as a document completed, a signature captured or a form approved. As you capture these you can link all the boxes together in order.
Creating detailed views of a process
Once we’ve described the high level process we can start to explore how it works at a more detailed level. Some people call these sub-processes or drill downs.
You don’t have to create a detailed view for every activity, it depends on whether you need to know more about that activity or not. If you do then this is how.
Simply click the detailed view icon on the what box.
You’ll immediately move to a new diagram. Look at the breadcrumb and you’ll see you’ve entered a new level of detail.
Now start drawing the next level of process. You can start your scope by dragging the inputs and outputs from the parent level onto the canvas from the Create menu.
Then follow the previous instructions to create flows.
If you need to create more details you can. There is no limit to the number of detailed views you enter.
Linking to relevant documents
As you capture a process you will want to add additional information to it. For example, document templates, systems or descriptions of the process steps.
All of these are easy to add in Skore. Every step in a process can have a text attachment or a link to another document or system.
To create a text attachment simply move your mouse over the step in the process and click on the paperclip icon.
Click Add New Text and enter the text you need. You may use markdown to format the text if required.
To link to a document or system use the URL link on the attachment window.
These are the basic steps to any process capture in Skore. We hope you have found it useful. If you have any further questions you can contact us at email@example.com . Follow us on our social media below for further hints and tips on how to get the best out of the Skore Digital Discovery Platform.
Skore, the Digital Discovery Software Platform is pleased to announce the relaunch of its training programme. The programme is designed and available to anyone who needs to capture and analyse processes within an organisation and is looking to improve their skills.
Craig Willis – Customer Success Director said ‘Skore helps organisations understand and clarify their processes so they can transform their businesses. We are delighted to have the opportunity to demonstrate how Skore can be used in live workshops to save time in process discovery and engage participants. Our training programme means participants can enhance their skills to extract insights, analyse processes and encourage collaboration with colleagues.’
At the end of the training, participants will be eligible to apply for the Skore Practitioner Certification. The first date will be held at the Future Technology Centre in Portsmouth on Tuesday 3rd September. This will just be the first of many dates announced as theSkoreteam roll out the enriched accreditation programme.
If you’d like to learn more about the Skore training and accreditation program please get in touch by emailing firstname.lastname@example.org for more information.
Digital Discovery Platform announces partnership with leading RPA Solution
& Services experts Lawrence & Wedlock.
The new collaboration will ensure an end to
end solution for companies looking to achieve agility in implementing RPA
technologies. Skore’s Robotic Assess module brings disruption to the discovery
phase of any automation project. It considerably reduces the time to discover,
engages stakeholders and produces a robust analysis of the current situation.
Lawrence & Wedlock, an experienced intelligent
automation services provider, delivers end-to-end solutions from process
discovery and product selection through to implementation and ongoing
In the rush to automate it’s not always clear what to automate now and what to improve before automating. Daniel Lawrence, Managing Director at L&W said: ‘Our clients rely on Lawrence & Wedlock to deliver agile, creative and efficient solutions. The Skore platform is becoming an integral part of our delivery toolkit in facilitating this, enabling us to move away from static templates and spreadsheets in favour of a robust, scalable platform to work collaboratively with our clients to deliver their RPA programme and provide our developers with everything they need to deliver automations.’
The Skore Digital Discovery tool is an excellent match for any organisation looking to become more agile through the use of disruptive technologies such as RPA. Chris Green, Partner Director at Skore said: “Skore is the answer for organisations looking to rapidly implement automation based on an in-depth analysis of their current situation and provide a solid foundation for ongoing adoption of that technology. Lawrence & Wedlock provide a comprehensive and effective solution for their customers using RPA which makes perfect sense for this partnership.”
Notes to Editors
Skore is a leading software company whose unique solution helps organizations reduce the cost and risk of digital transformation, systems implementation and automation.
Lawrence & Wedlock are a certified RPA services partner, providing automation Services and Solutions. Their objective is to make automation enablement truly accessible for businesses through our simple, flexible and effective services.
For further press information, please contact:
Anna Roebuck email@example.com
Marketing and Communications Manager 023 92 658 268
Following feedback and the continuous improvement of our platform we are delighted to announce updates to our Digital Discovery app. In the latest version you can discover the following enhancements:
Enhanced user experience and Performance (including Microsoft Edge) – streamlined login experience, page load time halved, more reliable in low bandwidth areas, increased user feedback with loading bar.
Custom Fields – improved ways to categorise and analyse requirements, risks, issues, ideas, questions etc.
Support for single sign on providers – Azure, Google and all Oauth compatible providers.
Did you know you can rapidly capture business requirements, issues, risks, questions and other information directly related to your process?
The custom field feature is available to all editors and lets you capture this information on the fly.
Custom fields can be added to the attachment panel. Simply enter the type of field you want to capture and add the details.
Now create a report and filter by your custom field to see a list requirements in the context of your process.
If you have any questions, or would like to learn more, please contact us on:
IDEFlite is the perfect way to communicate how a business process, and any underlying automation, is going to work between technical and non-technical audiences. This makes it an ideal point of reference throughout a project.
Audiences can use it to describe ideas, changes and potential issues in a way that reduces misunderstanding.
Unlike the typical flowchart modelling techniques, found in technical developments, IDEFlite is ideal for creating a high level view of a business process. It does so in a way that is easy to understand for anyone who needs to look at and comment on the model.
What is IDEFlite?
Based on IDEF0, IDEFlite is a simple, yet powerful, way to model activities, workflows and activities. It’s simple in that it uses a very limited notation which makes it easy to read for anyone.
While being very simple it can be used to describe extremely complex scenarios using decomposition. That is, every single activity can be described in more detail whenever required. Without the need for a complex library of descriptors.
When compared with IDEF0 one can see the primary difference is that IDEFlite does not make use of Controls and Mechanisms. Instead it focuses on Inputs and Outputs while including a human role.
How does it work?
The Building Blocks
Work is described as activities.
Every activity should have at least one input and output to set the scope of the work. All work should be owned by someone in the form of a supporting resource.
Activities are Linked Together
Work activities are linked together to form flow diagrams (processes).
Activities are Deconstructed to Form Hierarchy
Work activities can be deconstructed thereby creating a new detailed view of that activity. This forms a hierarchy of detail linking high level activities with low level tasks.
This is done when it is necessary to describe an activity in more detail. For example during a conversation about how something works. If the current flow does not adequately describe a particular interaction the user can take that step and create a detailed view.
Each level of detail is a new diagram, together this collection of hierarchically linked diagrams is a map.
We’ve never wanted to sit still and we’re always looking for ways to improve our company, our services and our products. Earlier this year we released the latest version of our Skore web application. This included an almost complete rebuild of the whole app from ground up.
It’s no small undertaking to start from scratch but we felt the time was right. As you develop a product there’s lots of trial and error, some things work well others, not so much. Feedback from users is essential but so is our own experience using the product. And this is something we pride ourselves on, we use our product on a daily basis.
But it’s not just user experience and usability changes that are important. As we develop the software we learn what works and what doesn’t. We realise that some choices, that seemed right at the time, have challenged us later on. This is why it’s important to take the opportunities to rebuild when they arise. To apply, from the beginning, all the lessons we’ve learnt since the last time.
For those that have followed us since 2014 they’ll know that this isn’t the first time we’ve rebuilt the product, or redesigned the user interface. Here are some of our previous user interfaces that some users will remember, some more fondly than others!
While not the very first prototype you can see one of the first uses of the what and why boxes. The product was then called Score with a C. All the main controls are there which allowed us to start testing with real users before we officially released.
Skore Version 1
Our first official release of Skore was for the desktop only. The interface was simple, there was no way to apply styles to the content. The editor tool bar was along the top of the application rather than the left bar we use now. By this time we had added the sticky note feature that allowed the user to annotate process models.
All the key features were here by this point, rapid modelling, shortcuts, multi-layers and attachments on each box. Although in version 1.0 you could only share processes by PDF or with other users of Skore desktop.
Skore Version 2
Following a business review with the Happy Startup School we underwent a rebrand, new logo and website. Then we decided to follow up with a redesign of the Skore user interface.
We worked with Mike C from Think.gg to design a new interface with darker colours contrasted with the green we had adopted in our logo and website.
We implemented a bright fun backdrop to the app which proved controversial. Some users loved the playful background and others immediately asked us to remove it. We quickly implemented a configuration item for those that weren’t fans.
By this time the app had implemented stylesheets that let users change the look and feel of the visualisations, add images or choose from the library of icons.
It was shortly after the release of this version that we started working on our first web app. To get up to speed as quickly as possible we build a separate backend web application and graphted the new Skore editor on top of it.
One of the biggest challenges for us is that we used different teams, and different designs, for the main web interface and the editor interface. These were completely different apps that had been integrated. It soon became clear that we’d need a complete rebuild to resolve the increasing technical debt that had built up.
Skore Version 3
Back in late January we released our Unity interface, or Skore version 3, which brings all parts of the application into a single design. This version of the interface has undergone the most extensive user testing to date. This led to a standardisation of common functions such as Search, New, Edit and Save across each type of content in the workspace.
The interface also came in time for our new branding which was easily implemented into the system.
This is a great step forward for us, it demonstrates our commitment to continually improving the product. It’s not just the interface but the rebuild ensures we also constantly update and improve the architecture, security and performance of the application.
At the heart of an agile organization is a deep understanding of how we work together. In an agile team, the constant collaboration between the members help doing so. Retrospective meetings are the institutionalised forum for talking about “how we work”. In reality, every time people talk together there is a little bit of “how” in the conversation. How many conversations end with “you do this, then I do that”.
There is little need to formalise processes in too much details at a team level. This is compensated by clear and open communication between the members.
Do you need processes at an organisation level?
This gets more complicated when several teams are working together (team = sharing coffee machine). Such as procurement and production; or sales and accounting. Or Head office – regional offices.
At this level, the interactions are less regular, and, we do not systematically voice concerns or “just” change how things work. Processes change are often heavy and it’s easier to not do it.
This is where process definition gets critical to understand how things work. And this is where you need some sort of governance to make it right, especially around change.
What is process governance in an agile organization?
This post finishes with a list of open questions / thoughts because I don’t have a definitive answer (yet).
Create a system that allows continuous improvement (CI) of processes (willingness to do so, and an approach to make it) at cross-functional level
Create the incentive to do CI across several teams (incentive = people will find the time to do it)
Have a common language to describe the work so that everyone can prepare in the best way (Hello, Skore)
Process owner is key role to make that happen
Middle management is a key role to make that happen
Good understanding of outcomes of the process vs. outputs to be in the right context
The key seems to be to create “space” in the organisation for continuous improvement activities…