Project Procedure

We support you – from analysis until implementation

– 6 to 10 weeks –

Analysis

– 12 to 16 weeks  –

Design

– 8 to 12 weeks –

Pilot

– + 8 weeks  –

Implementation

Typical deliverables

  • Strengths/weaknesses-profile
  • Quantified optimization potentials
  • Implementation roadmap
  • High-level concept
  • Detailed design for organization, processes and IT
  • Implementation plan
  • Proof of concept
  • Need for conceptual adaptations
  • First benefits and quick wins
  • Benefits according to implementation plan
  • Potential from continuous improvement process (CIP)

– 6 to 10 weeks  –

Analysis

– 12 to 16 weeks  –

Design

– 8 to 12 weeks  –

Pilot

– + 8 weeks  –

Implementation

Success factors

  • Defined project targets
  • Project-specific tools and methods from the “consulting toolbox”
  • Clear project structure
  • Early integration of operational teams
  • Permanent focus on the defined targets
  • Stakeholder involvement
  • Close on-site support
  • Readiness for concept adaptations (theory follows reality)
  • Clear performance KPIs
  • Thorough handover to the implementing organization and teams

Our Value Proposition

The sustainability of the solution is our focus from day one.
For this purpose, we use pragmatic concepts that are individually tailored to our customers' specific needs.
Affected employees are included early as part of our integrated Change Management.

 

Methodology

Sustainable projects are enabled by using the right tool at the right time

Design

Analysis

  • DILOs to survey the as-is situation
  • Structured interviews to verify/falsify hypotheses
  • Organizational analysis
  • Value Stream Mapping as basis to identify waste
  • Business Case to quantify potentials
  • SWOT-analysis
  • Analysis of P&L and balance sheet
  • Methodological trainings to train project-relevant basics


  • Brownpaper-sessions to develop processes
  • RACI-matrix to allocate responsibility
  • ABC/XYZ-analysis to derive product-specific recommendations and strategies
  • Process-analysis to define IT-requirements
  • Spend-analysis to detect cost saving potential
  • Workshops with suppliers/ customers to verify potential solutions
  • Business- and IT-concept to display the future solution in a consolidated way

Implementation

Pilot

  • Roadshows to mobilize stakeholders
  • Regular Gemba-walks to secure the implementation at shopfloor-level
  • Coaching of selected team members
  • Workshops to discuss lessons learned and to detect necessary concept adaptations
  • Specific content trainings  to teach new processes and ways of working
  • Testing of IT systems to secure functionalities
  • Tracking of KPIs to evaluate the success of the project
  • Methodology to collect employee suggestions to ensure continuous improvement
  • Audits to evaluate the maturity of the implementation