KnowHow is a configurable Learning, Performance & Talent Development Platform that connects learning, performance, skills and growth in one integrated environment.

Organisations can use the capabilities they need and configure roles, workflows, structures and experiences around how they operate.

KnowHow is best suited to organisations that want to manage learning, performance, skills and competency development in a way that reflects how their organisation actually works.

Some organisations may begin with a focused requirement, such as learning management, compliance training, performance development or skills development. Others may be looking for a broader platform that connects several of these areas within a single environment.

KnowHow can be configured around the organisation's own structures, processes and priorities, allowing the platform to support the capabilities that are needed now while providing room to expand as requirements evolve.

A conventional LMS usually centres on assigning, delivering and tracking learning. KnowHow includes that foundation but extends it into connected performance development, skills and competency development, assessments, events, CPD, reporting and related organisational workflows.

The emphasis is on connection and configurable fit rather than simply adding more features to a course-delivery system.

Yes. An organisation can begin with a defined priority such as learning management, onboarding, performance development or a targeted capability programme and expand its use as requirements evolve.

The starting point is agreed during discovery so the implementation can remain focused and proportionate rather than broader than the organisation needs.

Yes. KnowHow can be considered as a replacement for an existing LMS where the required learning, administration, reporting and related development workflows are within the agreed solution scope.

The replacement conversation starts with what needs to be preserved, what should improve, and which existing processes should not simply be carried forward unchanged.

Migration can include agreed users, suitable learning content and relevant historical learning information where the source data, format and target requirements support it.

The migration scope is confirmed after reviewing the source system, data quality, business value and what needs to remain accessible after transition.

Yes. KnowHow supports established eLearning standards including SCORM 1.2 and SCORM 2004, with other supported standards considered where appropriate.

Existing packages should be reviewed as part of transition planning so compatibility, completion behaviour and any historical-data requirements are understood before migration.

Transition planning is scoped around the existing environment, the information and content that must move, configuration requirements, testing, administrator readiness and the agreed go-live approach.

The aim is to manage the change as a controlled implementation rather than treating migration as a simple file transfer.

Yes. Learning can be structured into sequenced journeys and Learning Paths, while live or virtual events can sit alongside digital learning, assessments and follow-up activity.

This allows programmes to combine self-paced learning, workshops, webinars and practical development in one coordinated journey.

KnowHow supports assessments and evaluations within the broader learning journey, together with certification and continuing professional development processes where required.

The configuration can be aligned to the organisation's programme, role and compliance requirements.

Yes. Performance Development Reviews can support objectives, feedback, review cycles, behavioural competencies and ongoing development conversations rather than treating performance as a once-a-year event.

The process can connect performance activity with learning and development actions where that reflects the organisation's approach.

KnowHow supports skills and competency development structures that can be aligned to roles, development needs and organisational priorities.

Specific review, rating and gap-analysis processes should be demonstrated against the organisation's requirements and the current configured product.

Yes. The connected-platform approach can help organisations link identified development needs, role requirements or performance priorities to appropriate learning and development activity.

Exactly how those links are configured depends on the organisation's workflow and the capabilities being used.

Organisations can bring suitable existing learning into KnowHow, use standards-based eLearning such as SCORM packages, and create new learning through KnowHow's content-creation capabilities.

The appropriate mix depends on what the organisation already owns, what needs to be maintained or refreshed, and where new content is required.

KnowHow supports administration of users, roles, groups and organisational fields within the agreed operating model, including bulk user-data handling where appropriate.

The administration approach should reflect how starters, leavers, role changes and organisational updates are managed in the client environment.

Yes. Roles, groups and organisational context can be used to target relevant learning and support repeatable assignment rules where configured.

This can reduce repeated manual enrolment work while keeping targeting aligned to the organisation's structures and policies.

KnowHow supports practical course maintenance so learning can be copied, updated and versioned without rebuilding every programme from the beginning.

This is important for organisations that maintain recurring, compliance or frequently updated learning over time.

Administrators can use progress and overdue visibility, reminders, dashboards, filters and downloadable reporting to support day-to-day follow-up.

Reporting can be viewed in the relevant organisational and programme context rather than relying on parallel spreadsheets for routine monitoring.

KnowHow can be configured around organisational structures, roles, permissions, workflows, terminology, branding and programme requirements.

Configuration is intended to fit the platform to the organisation while maintaining a controlled and supportable product environment.

KnowHow supports integration approaches including SSO and established connections used for learning and event workflows. Wider HRIS, identity, calendar or business-system requirements are scoped against the specific client environment.

Yes. KnowHow can be configured to reflect organisational structures, companies, groups, roles, reporting context and permission profiles within the agreed operating model.

This allows the platform to support organisational complexity without requiring every user to see or administer the same information.

KnowHow uses AI-assisted capabilities to support activities such as content and assessment creation. The design principle is human-controlled: administrators and learning teams retain review, refinement and approval responsibility.

AI is used to reduce effort and support better workflows, not to remove the people responsible for learning, performance or governance.

KnowHow is delivered as a cloud-based SaaS platform using Amazon Web Services, with role-based access and client-specific technical requirements reviewed during implementation and due diligence.

Security, architecture, data-processing and integration requirements should be validated against the current environment and the client's own standards.

Implementation begins with understanding the organisation's priorities, users, structures and workflows. The agreed solution is then configured, prepared for deployment, supported through training and go-live, and refined as the organisation learns from use.

The implementation plan is shaped around the selected scope rather than applying one identical rollout to every client.

Yes. Implementation is scoped around the agreed requirements, from a focused learning deployment to a broader connected learning, performance and skills environment.

The aim is to solve the priority well and expand where there is value, rather than introducing unnecessary complexity simply because the platform can support more.

KnowHow provides in-depth training to the people who will administer and use the platform, together with a dedicated Customer Experience Representative for ongoing support and coordination.

The approach emphasises practical enablement and a continuing client relationship rather than relying on generic support materials alone.

There is no single responsible answer without understanding the scope. Timing depends on configuration, integrations, migration, content readiness, stakeholder availability, testing and the rollout approach.

A tailored demonstration and discovery conversation are used to understand those dependencies before an implementation plan is proposed.