An organisation in Insight represents a business that is using Insight to deliver a change initiative. Everything in Insight happens within an organisation.  

The organisation itself will created by an Insight team member and the organisational master data will be created and maintained by Insight Admin user. However, it is important to identify and maintain all relevant associated master data.

If there are internal systems where this data is already maintained and accurate, discuss with the Insight Engineering Lead to understand whether an integration can be created to minimise maintenance activities.  

Core Data (Organisational Master Data)

In any transformation project, core data serves as the bedrock upon which successful change is built. This essential data encompasses a wide range of information, within Insight we have broken this down into:

Inputting core data into Insight is easy, to access core data, as an owner (see the permissions section below for an explanation into the various permission levels within Insight) click on the settings wheel on the bottom left of Insight, which is always visible, and select “core data”.

Business areas and locations are inputted via a branching, free-text, editable, tree. You can add as many branches and layers as you like, and once inputted, these areas and locations can be pulled through onto the action and impact grids within Insight.

Roles, Action Types, Impact Types, Labels and Stakeholders are input via premade digital forms with clear instructions as to what data needs to be provided, a red star by a section title means that this section is required to be filled for the creation of the specifically selected data set.

Creating a Programme 

A Programme in Insight represents a collection of related projects. Whilst the use of programmes is not mandated, it can be useful to group related projects into programmes to achieve a portfolio level view of change happening throughout an organisation. This can enhance management oversight, enable portfolio-style reporting, and can be particularly helpful where multiple initiatives impact many of the same audiences.  

The following fields are populated when a programme is created:   

Programme Name : the title you wish to give to your programme

Programme contact: must be a Insight system user already created in the system 

Programme Sponsor: must be a stakeholder already created in the system 

Start and end dates: clarification of programme kick-off and planned end dates 

Project status: dependant on start and end dates will be ‘Not started’, ‘In Progress’ or ‘Complete’. 

Description: provides a top line overview of what the programme is – you can apply most types of formatting to this section, including hyperlinks 

Objectives: each programme by default is allocated three objectives. Due to this area being a free text field you are not limited by this number but as a minimum it is recommended to list at least three to clearly outline what the programme is aiming to achieve. 

Projects: if you’ve already created projects that are associated with the programme, you can use the search box to look up the title of these and assign them to your programme. If you’re yet to set these up, you can do so later from the newly created Programme Overview page. 

Programme milestones: can be used to identify key events that will appear on the programme timeline. Any milestones added will also appear on the overall organisation timeline.  

Creating a Project 

A Project must be set up in Insight to track impacts, actions and stakeholders. 

A Project in Insight is an initiative by the organisation to realise a set of benefits. Projects are used to identify impacts, actions, and track mitigations to ensure a successful outcome. 

Projects can be added to a Programme or can sit directly under the Organisation where no Programme is set up. 

Project milestones can be used to identify key events that will appear on the Project timeline. Any milestones added will also appear on the overall Programme and Organisation timeline.