Product Update June 2019

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:

+44 (0) 2392 658 268 

or email us at [email protected] 

From the Skore Product Team


Why do we need IDEFlite?

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.

Skore natively supports the use of IDEFlite, why not request a demo to see how.

How we keep Skore at the cutting edge

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!

Skore Prototype

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.

If you would like to learn more about Skore why not request a demo.

Process governance and agile

Do you need processes at team level?

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…

To be continued.

Possible service interruption – June 13 2018

Some users of Skore may have experienced a temporary service interruption at approximately 2pm British Summer Time on Wednesday June 13th 2018.

This was caused when a name server, unconnected with Skore, was configured with incorrect domain resolution information. This in turn caused the domain to be redirected to a holding page that read “Hello World!”.

The issue was discovered, reported to the owner of the domain name service, and resolved within 60 minutes.

Temporary suspension of justskore.it publishing from desktop app

We would like to inform all users of the Skore desktop application that the anonymous publishing feature justskore.it has been temporarily suspended since March 20th 2018. This has been caused by a change to one of the third party services that this feature is based on.

We will be returning the service as soon as we have completed the necessary updates to the product.

What is it?

The justskore.it feature in the desktop software allows a user to quickly and anonymously publish a .skore file to the internet. Anyone with the link can view the process created in Skore online.

The advantage of this feature is that you can quickly share ideas to anyone with an internet connection and a web browser. The downside is that the information is shared publicly and cannot be changed once it has been published.

How does it work?

The features uses https://github.com/ and saves the Skore xml data as a publicly available anonymous gist on the github service. As of March 20th 2018 github have ceased support for anonymous publishing therefore blocking Skore desktop app from publishing new processes to the service.

All previously posted processes will remain available. You can read more about the update from github here: https://blog.github.com/2018-03-20-removing-anonymous-gist-creation/


We are currently working on a new version of the Skore desktop software. This will include a new version of this feature which will allow publishing and sharing of the processes to our own servers. This will have the advantage of providing us more control over the data inline with data protection guidelines.

We are working to release this new version of the software over the next few months.

In the meantime users may consider saving your process as a .html file and uploading it to a service such as Sharepoint, OneDrive or WordPress.

Alternatively users should consider our web service. The Skore web service offers the ability to create and publish processes anonymous with the added advantage of being able to edit and update the process once published. This essentially means you can maintain a single URL link for any users to accesses the content. Examples of this feature include sharing processes embedded in a website or training material.

Our new freedom pricing model maybe suitable for users of the desktop software. Check out our pricing page for more information.

If you have previously purchased the desktop software we would be happy to talk about a discount to your first year.

For further information please contact [email protected]

Skore service interruption – March 22nd 2018

The main Skore service (https://app.justskore.it) suffered a short interruption at 15.07 GMT today and lasted up to 20 minutes for some users.

Those editing or viewing processes would have seen several error messages including; Server Unavailable, Proxy Error and 503 error.

The outage was caused during a routine reboot of servers in order to apply security patches to protect against the Meltdown and Spectre vulnerabilities.

Rebooting the servers took longer than anticipated which led to longer outage of the core Skore services. The knock on effect was that some services became temporarily unavailable.

We are reviewing our risk analysis for maintenance to ensure that we are taking all necessary precautions for future maintenance so that we can better inform customers during such updates.

We apologise for any inconvenience this may have caused.

Skore service interruption – March 7th 2018

Skore web service suffered a limited interruption shortly after 1.30pm GMT today. The interruption lasted approximately 10 minutes and affected around half of all active workspaces.

Users viewing and editing content would have been unaffected although they may have seen a warning message saying the server was unreachable. Users browsing the workspace and moving between content would have experienced 404 warning messages and may have been logged out of the system.

The issue was caused when one of our load balancers failed to redirect traffic away from one of our servers undergoing routine maintenance. We are continuing to investigate the load balancer failure.

2017 Review – Management Changes and Growth at Skore

Once again I am glad to say that we are at the end of the year and looking back with a very positive view. 2017 has seen more changes, activity and growth at Skore.

Here is an overview of the key highlights for 2017 at Skore.

Our Partners and Community

We started shifting our focus to partners in 2017 which has been challenging and exciting. It became clear in 2016 that we needed a larger team to support our growing customer base. This meant growing our team internally or working more closely with partners to provide these resources.

As we decided to focus internally on the product, and supporting tools, we were relying on our fantastic network of partners to provide additional services to our clients. This has worked well and we are looking to extend this further into 2018.

To support our network we setup our Skrum events running the first in July. These have proved very popular with both partners and customers and we will be increasing the frequency and availability of locations in 2018.

The Company

Early 2017 brought a lot of changes for us internally as we made some structural changes to the company in order to support our growth. The previous make up of the company makes it hard to do an exact comparison for year on year revenue although all calculations show revenue has more than doubled in 2017.

In February we expanded the management team with the appointment of Chris Green as our Director of Partnerships. Chris brought a wealth of experience in delivering value added solutions to customers. His position supports our approach to developing deeper and more collaborative relationships with our partner network.

During the year we also increased our development resources adding another full time software developer to the team. This is a front-end role for the software and supported the development of our new release due in January 2018.

Finally, at the end of 2017, we welcomed Antony Bream as an advisor to the management team. Antony has experience in managing technology companies through growth providing strategic guidance, marketing insights and an extensive industry network.

The Product

Following the launch of Skore web app at the end of 2016, early 2017 saw the addition of a number of improvements to the product. These included features such as commenting, approvals change history.

The rapid growth in users meant we had to review and improve the infrastructure early in the year. In August 2017 we implemented a completely new architecture for the product that will allow much more secure and scalable growth into the future.

The final major project of 2017 was a complete redesign of the software. Sneak previews have been available through a series of webinars. The first customer trial workspaces were available in December 2017 and a formal launch is due in early 2018.

So once again 2017 has been another exciting year us and we look forward to welcoming 2018 along with our partners and customers. Wishing you all the best for 2018!

The team at Skore.

Skrum – a new way to share ideas and meet likeminded practitioners

Definition of Skrum in English:




  1. A gathering of business change and improvement professionals in an open discussion where ideas are shared and questions are answered. A Skrum typically takes the form of three talks followed by discussion, questions and networking. Talks are 20 minutes long and cover topics such as project insights, case studies, methodology and technology reviews.

Partly inspired by Product Tank, product management meetings, and by our network of partners we decided to start hosting our ‘Skrum’ meetups this summer. When we meet individually with partners and customers we have some great discussions and always learn something new.

But we realised that there was a lot of similarities between the discussions we were having. So why not bring some of these people together to have the same conversations and share their experiences in order to help each other learn?

And so Skrum was born, a small(ish) gathering of practitioners in a room together to explore topics that can benefit and help in their own projects.

To bring a bit of structure to the events we decided to shape it around a series of talks that allow us to discuss these topics from different angles. Each session we try to have one talk from each of these areas. The main areas to date are; Project Insights – a case study or introduction to a particular project you have worked on. Methodology Review – an overview of a tool, or framework, you have used successfully. And Technology Review – an introduction to a relevant technology that has helped you deliver a project.

So far we have held our meetings in central London but we plan to run more in other cities. In fact our next meeting will be at our headquarters in Portsmouth on the south coast of England.

If you’d like to get involved and learn more about our upcoming events then why not join our meetup.com page.