Rows of ring binders on office shelves.

Home · Work · E-commerce

A retailer turned manager memory into documentation its teams and ERP could use

Case study · E-commerce · Knowledge management

A pre-owned consumer electronics retailer ran on manager memory, chat threads and spreadsheets. We built documentation tied to accountability and to its ERP build, including a requirements survey for seven departments.

Client
A pre-owned consumer electronics retailer selling online and on marketplaces
Engagement
An operating knowledge base: policies, SOPs, role definitions, manager SLAs, weekly reporting and ERP requirements
Result
Reusable documentation across several major transformation areas, and less dependence on undocumented manager knowledge
How we worked
Embedded with department managers, documenting processes while they were still changing and tying each document to a role, an SLA or an ERP requirement

Published . Client name withheld.

7 departmentscovered by the ERP requirements survey we designed

The situation

The retailer sells pre-owned consumer electronics online and on marketplaces. Its operations had grown faster than its internal documentation. Processes, decisions, policies, SOPs, responsibilities, ERP requirements and reporting structures were scattered across conversations, spreadsheets and managers’ memory.

Critical processes were undocumented or documented inconsistently. Staff relied on memory, chat messages, spreadsheets and verbal instructions, and new hires and managers had no single source of truth. At the same time, ERP development needed clear process definitions that did not yet exist in a mature form. The business needed its tacit operating knowledge written down in a form that could support training, accountability, ERP implementation and management control.

What made it hard

  • Documentation had to be written while the processes it described were still changing.
  • Some departments understood their work informally but could not yet express it as structured requirements.
  • The same knowledge base had to serve two audiences: the people running daily operations and the team developing the ERP.
  • Teams were at different levels of process maturity, and SOPs, key result areas (KRAs), job descriptions, policies and ERP requirements were not consistently connected.
  • Every document had to be practical enough for managers to use, not just polished for leadership.
A hand writing notes in a notebook at a desk.

How we worked

We worked inside the business with its department managers and scoped the work around what the transformation needed next, not around documenting everything. Each document was judged on two things: could a manager use it, and did it connect to a role, a control or a system requirement?

  1. 01

    Start from what the change needs

    We built documentation around active transformation needs: policies, SOPs, requirements, weekly reports, SLAs, role definitions and ERP specifications. Knowledge management was treated as an operational control system, not an administrative archive, so each document had a job to do.

  2. 02

    Capture how work really happens

    We used manager surveys and structured requirement gathering to capture each department’s needs in its own terms. The ERP requirements survey we designed covered seven departments: HR, procurement, order fulfillment, warehouse, accounting, customer support and IT.

  3. 03

    Tie documents to accountability

    Manager SLAs referenced the current SOPs, policies, KRAs and job descriptions, so commitments pointed back to the documents that defined the work. We drafted policies covering SKUs, SLA structures, nondisclosure and non-compete language, user access and permissions, coupons, the customer dashboard and the trade-in program.

  4. 04

    Feed the ERP build directly

    We linked documentation outputs to the design of the ERP and to operational accountability, so process definitions served the software team as well as the people doing the work. While the ERP was being built, we supported task documentation in a task management tool as an interim execution layer.

  5. 05

    Make weekly reporting repeatable

    We created and refined a weekly activity report format covering activity overview, operations, marketing and strategy, discussion points, deliverables and next steps. Weekly updates followed one repeatable structure instead of being put together ad hoc.

The results

Measured against the outcomes agreed at the start.

7 departments
  • Created reusable documentation assets across several major transformation areas, from policies and SOPs to role definitions and ERP requirements.
  • Designed an ERP requirements survey covering seven departments: HR, procurement, order fulfillment, warehouse, accounting, customer support and IT.
  • Improved cross-functional clarity for ERP development, HR accountability, warehouse process control and reporting.
  • Connected manager SLAs to the current SOPs, policies, KRAs and job descriptions.
  • Replaced ad hoc updates with a repeatable weekly report format.
  • Reduced the business’s dependence on undocumented manager knowledge.

What leaders can take from it

  • A knowledge base only creates value when it is tied to execution, accountability and system design. Treat it as an operational control system, not an administrative archive, or it will not change how work gets done.
  • Document how work actually happens, not how leadership assumes it happens. Manager surveys and structured requirement gathering surface the informal knowledge that an ERP specification depends on.
  • Current, version-controlled documents matter more than one-time policy creation. In a transformation, documentation is the bridge between strategy, process, software and people, so it has to keep pace with all four.

Questions about this work

How do you build a knowledge base that managers actually use?

Tie every document to execution, accountability or system design. For a pre-owned consumer electronics retailer, Armstrat built documentation around what the transformation needed next, including policies, SOPs, role definitions, manager SLAs and ERP specifications. Manager SLAs referenced the current SOPs, policies, key result areas and job descriptions, so the documents became part of how work was managed rather than an archive.

What process documentation does an ERP build need?

It needs clear process definitions for each department, written as the work actually happens rather than as leadership assumes it happens. For a pre-owned consumer electronics retailer, Armstrat designed a requirements survey covering seven departments: HR, procurement, order fulfillment, warehouse, accounting, customer support and IT. Structured requirement gathering helped teams that understood their work informally express it as usable requirements.

Bring us the hard problem.

We agree the outcomes first, then work inside your business until they hold.