Please enable JavaScript.

Coggle requires JavaScript to display documents.

Archetypes - Coggle Diagram

- - - - Uncertainty breads anxiety
      - Uncertainty sucks in time
      - Very little idea what is actually happening in the process
    - - Collaboration with supplier / Bloom
      - Negotiated T&Cs
    - - Too many contact points
      - Bloom teams all have narrow picture, can answer some Qs then directed elsewhere
  - - - Easy to follow
      - Easy to understand what is happening
      - Simple process, easy to communicate
        
        Flaq Qs (Bloom & Supplier) quickly and easily
      - Get through the process quickly
      - Know when there is an exception early
    - - What is happening and what they need to act on
      - What they communicate to stakeholders
      - Removes anxiety checking
    - - Know when something is going wrong before it happens
  - - - Which are 'In Progress'
      - When actions are due
    - - Linked to an invoice
- - - - Remove mental load caused by uncertainty
      - Automatic process from point of entry
      - Actionable insight - told what to do and when
      - Standardised high level process, variations below managed automatically
    - - Contract rigour assured
      - Compliance risk take care of
    - - Tell me the actions when needed
      - Clear picture of the pathway
        
        Variable depending on input (i.e framework)
  - - - Subtasks
      - Bell curve mgt
    - - Build based on inputs (i.e. framework)
      - Visual & clear
      - Breakdown of projects at stages
  - - - Buyer lacks sight of the supplier ITT response/Payment Schedule
      - Spec = milestones, SDP = setup varies as per billing (weekly, monthly etc) so it doesn't match to the buyer PO and causes confusion as per the original brief and milestone info doesn't pull onto the inv as per original brief
    - - Process
        
        Black hole when it comes to critical path
      - Contact points
        
        Different teams
        
        Multiple channels
        
        Confusing accroynms
        
        Multiple IDs
    - - Infrequent use, rel- earning
      - Don't want to spend time doing
      - Don't want to spend time learning
      - Don't want more technology
    - - Sight of what has been processed
      - Sight of what is due
      - Sight of What is coming
    - - Ego "I know my area, who are you to tell me" / Inability to answer Qs
      - Lack of context
      - Lack of time
      - Lack of knowlege
- - - - Too many exceptions/branches
      - Compliance
        
        Unclear on insurances etc
      - Contracts: current data quality is poor (i.e. call off date missing)
      - SDP
        
        Approved?
        
        Due for payment?
        
        Don't understand the payment terms
        
        Paid
        
        MF invoice sent separately
      - Accreditation
        
        Not through / real accreditation
    - - How to respond is vague (attachments)
      - Difficult for SMEs
      - Creating winning responses
  - - - Simplify the tender response
      - Transparency over payment
    - - What share of our business
      - Insight into client portfolios
      - Year on year trends
      - Anonymised view of pipline
- - - - Managing compliance across multiple frameworks
- - - - Oversight of all my procurements (Critically up engage)
      - What money is on POs
      - Pipeline money coming in
      - Invoices due
      - Project Mgt
    - - Data
        
        Poor data quality
        
        Lacks issue flags, too much inference
        
        Bloom KPIs /Added Value MI
        
        Savings
        
        Added Value
        
        Resource Savings
      - Process
        
        Limited to for value add
        
        95% off time not value add
        
        Customer expectations not set
        
        KPIs
        
        Process visibility in system
        
        CX
        
        Many handoffs
      - SDPs
        
        Single source of truth
        
        Aged debt
      - Specs
        
        Time Vs Quality
        
        Late sight = buyer urgency = Bloom pressure
    - - Stories
        
        Ability to tell stories to clients
      - Issue Resolution
        
        Proactive issue identification
        
        Issue flagging
    - - Taiolred view - what is happening with my projects?
      - Collaboration
      - Spec
        
        Access and support early
      - Enforce critical path blockers on the process
        
        Clearer path for 'urgent' projects
  - - - Manual Inputting
        
        Project Creation
        
        ITT Creation
        
        PO Setup
        
        SDP Setup
        
        Contract Setup
        
        Results in data quality issues
      - PO
        
        Mixing up models - T&M / Milestone - might be a T&M or Monthly billing, we the profile against milestones etc = everyone gets confused
        
        Or, have milestones but the payment schedule is monthly and submit monthly
        
        Money moving all the time = confusion & risk
    - - Consistency