Overview


A Project in LINQ serves as a structured workspace that allows you to develop, test, and refine models without modifying the original data in the current state. Projects are particularly useful for scenario testing, enabling iterative improvements before implementing changes in real business environments. 


When a project is created, all existing current state models are automatically included in the project:

  • Model Independence: Changes made within a project do not impact the original current state models. A copy of all relationships is created for the project model automatically.
  • Controlled Modifications: If a node is changed in a project model, the update is stored only in the project, keeping the current state unchanged.
  • Scenario Testing: Projects allow you to test, iterate, and refine models before applying them to real business processes or replacing current state with the future state.  


Creating a Project


To create a new project: 


1. Navigate to the Workspaces, select Create project from the available options.  Or you can create a new project directly from Organisation projects card by clicking Create project.  

2. Name your project, provide a summary of the project purpose, start date (required), and completion date (optional).


2. If enabled by toggle on/off, the project can operate in sandbox mode, meaning models created within the project remain completely independent of the current state without impacting any existing insights.  Sandbox is useful for experimental modeling without affecting existing models. 


  • If a project is created in sandbox mode, the Sandbox column in the Organisation projects card will display "true".


  • Existing current state models will not be listed in the Models card within the project if a project is created in sandbox mode. When opening the Models page inside a sandbox project, the list will initially be empty, and you can create new models that are completely independent of the current state.  

Note: Currently, models created within a sandbox cannot be directly transferred to a real project environment. Since sandbox projects are entirely disconnected from the organisation's current state, there is no built-in functionality to move or push models out of the sandbox. 


  • While sandbox models cannot be pushed to the real environment, but you can still upload models for testing and refinement.  This allows you to experiment with different scenarios without affecting live data.


3. If a project is not created in sandbox mode, it retains a connection to the current state models. Once the project is saved, its home screen background will appear in gold color, indicating that the project is in the Project environment.

  • Overridden models within the project are displayed with red icons to differentiate them from unchanged models. 

 

Bringing Models into a Project


Here are the steps to bring models into a project:


  • When a project is created, the Models card will now display all existing current state models.  Unmodified models retain their original color as black.  Modified models turn red, indicating that they have been altered in the project. 



  • You can toggle the Filter unchanged models switch to focus only on models that have been modified.


  • In the Organisation view, you can easily identify which parts of the project have been modified. Red icons indicate models that have been changed as part of the project, while unchanged models retain their original colors. This allows you to quickly distinguish between models that are actively being worked on and those that remain unaffected but may still be impacted by the changes. 


  • Click on the models to bring them into the canvas, where they remain linked to their original current state counterparts, allowing you to modify, compare before-and-after states, and structure workflows without affecting the live business processes, as all changes are stored within the project workspace. 


Mapping the Future State Models a Project


When modifying a future state model, changes reflect how the process will evolve based on new tools, workflows, or automation. Thus, your adjustments may include new data requirements, process steps, or role changes, impacting how both existing and new roles interact with the system.  


The project modeling feature allows you to easily track modifications made to a model. 


Key features include: 

  • New content added to the model in the canvas is marked with a green dot, indicating a change from the current state.  You can drag the new change nodes with the green dot into the canvas and start drawing the new changes as they create the current state models. 



  • Unnecessary processes, information data, roles, and systems can be removed or deleted as new changes are added to improve process flow. 


  • Duration and frequency of actions can be updated for both unchanged and newly added changed action nodes, adjusting time and occurrence patterns to reflect efficiency improvements.

 

  • Cost reductions and increases are automatically updated, reflecting the financial impact of process changes and improvements.  Red with a downward arrow indicates cost reductions, showing where expenses have decreased. Green with an upward arrow indicates cost increases, highlighting areas where costs have risen due to process changes. 


You can click on Show Labels and select the Cost option to view these updates dynamically within the model.


  • You can visually compare the current and future state models side by side, identifying key differences in workflows, roles, and systems.  For more information, please refer to the Insights section.  


  • Changes are automatically flagged, allowing quick identification of updates in process steps, information, and automation. 


  • Once changes are validated, the Replace current state button allows you to finalize the project and apply the future state as the new current state.  This ensures that the digital model remains up to date, eliminating the need to rebuild a new current state model for future changes.  


Case Study: Transforming the Market Reporting Process with Future Modeling


Let’s use the below example of Demo Org to understand how future state modeling helps optimize a marketing report process. 


  • Current State Overview

In the current state, marketing reporting relies on manual processes, with data collected and updated through Excel, requiring frequent inputs from the Marketing Admin and Accountant. Generating reports involves pivot table updates, manual approvals, and multiple steps, slowing decision-making. The weekly marketing report takes significant time due to redundant actions and manual interventions.  


  • Future State Improvements

In the future state, the marketing reporting process is faster, automated, and easier to manage:

1. Excel is replaced with Power BI for dashboard analysis and marketing list updates.  

2. New customer additions are automatically processed and reflected in Power BI, reducing duplication. 

3. Publishing to weekly marketing report and analysing dashboards are automated, streamlining updates.


To apply these improvements, follow the steps below:

  • We draw these changes in the Project canvas and click Save to capture the updated future state model.  

  • Turn on the Show labels option to see cost reductions and increases directly within the model.  For instance, Power BI replaces manual Excel-based processes, significantly reducing reporting costs.  The cost of publishing the marketing report drops by $756. Marketing Admin costs decrease by $13,587 as automation reduces manual approvals.  The green upward arrows show increased costs for the website system and Power BI due to automation improvements, making publishing and data analysis automated. 


  • Click on the Open insights (right panel) button. This will display a detailed comparison between the current state and the improved future state.


Key Comparisons:

  • Processed Items: The number of processed items remains the same for outgoing data (104), but incoming data has decreased from 52 to 26, reducing manual inputs.
  • People Time (Hours): The total hours required for work has decreased, showing a reduction in capacity needs by 348 hours.
  • Cost (Dollars): The total cost has decreased from $18K in the current state to $15K in the improved model, reflecting a $2,279 reduction.
  • Value: The total value output has decreased slightly, from 572 to 520, but remains optimized based on process needs.
  • Carbon Emissions: The carbon impact has slightly increased from 770 kgCO2e to 779 kgCO2e, suggesting additional Power BI system use.

  • Workload Distribution: Marketing Admin still manages 3 actions, while Power BI handles 2 actions.  There is room to shift more work to automation. 
  • Automation Potential: 0% actions automated, no actions have been automated yet, showing an opportunity to reduce manual effort and improve efficiency. 
  • Data Supply & Value: Info supplied decreased by 33%, but high-value steps doubled (+100%), meaning fewer but more impactful steps.  


People and System in the Project


In the Project Environment, updates made to People, Systems, and Roles in the People and Systems model are automatically reflected throughout the entire project. This ensures that any changes—such as renaming a system, updating a role, or modifying organisational structures are consistently applied across all linked future state models.


How It Works:

  • The People and systems model captures roles and the systems they use.  You can also add and introduce new systems, roles, and infrastructure to reflect changes in business operations. 


  • When you update People, Systems, Roles, Infrastructure in the People and systems model, it automatically updates everywhere it is used.  For example, if an organisation replaces Excel with Power BI, updating this change in the People and systems model will ensure that every instance of Excel in all linked models is renamed to Power BI. This eliminates the need to manually edit each process where Excel was previously used in the project environment.