Your method: your problem-solving steps in SolveR.
If your company or your customer prescribes its own problem-solving procedure, we build it in SolveR as your method: you send the procedure and your report template, and we build the steps. We trial the method on one of your cases, and after go-live it writes into the same knowledge base as every other method.
When to use your own method, and when a standard one
Your own method makes sense when your company or your customer prescribes a procedure that matches none of the standard methods: the steps are different, they have other names, or the report has to follow its own format. That is the case for suppliers whose customer prescribes its own 8D form in its supplier instructions, and for companies that have their own procedure written into their quality system. If your procedure matches a standard one, you start with the standard method.
Your own 8D form, today and with SolveR
Example: a company handles complaints with its own 8D form, with its own deadlines for each step and with a separate technical and system cause.
| Today | With SolveR |
|---|---|
| The engineer works in a generic 8D template, because the tool only knows the standard steps. | The steps in SolveR are the steps of your form, with the same names and in the same order. |
| The form asks for a separate technical and system cause, while the template has one field for the cause. | The technical cause and the system cause each have their own step, as your procedure requires. |
| At the end the engineer copies everything into the company form and fills in the deadline dates by hand. | The report comes out in the format of your form, with every field the form asks for. |
| The completed form ends up in a folder where the next engineer will not find it. | The closed case goes into the same knowledge base as your 8D and PDCA cases. |
The example is made up and does not describe any customer.
What you get
A method in SolveR with the steps of your procedure, a report in the format of your template, and a record of every closed case in the knowledge base. The team works through steps it already knows, and the customer or auditor gets the report in the format they ask for. Nobody writes the report twice, once in the tool and once in the customer's form.
For each case the team picks the method that fits it: yours or one of the standard ones. The procedure stays yours: the steps, their names and the report format are the ones your company or your customer prescribes.
Four steps to your method
- 1You send your procedure and report templateThe procedure your team works by today, and the form your customer or your company requires
- 2We build the stepsWe build the steps of your procedure in SolveR
- 3A trial on one of your casesWe trial the method on a real case from your team
- 4Go-liveWe switch the method on for your team, and its cases write into the knowledge base
At the trial you judge for yourself whether the method runs the way your team works. Only then do we go live.
One knowledge base for every method
Your method writes into the same knowledge base as every other method. What a case in your method teaches is there for 8D and PDCA too, and the other way round. When someone describes a similar problem, cases from your method come up among the similar solved cases, and you search all of them with Brain. So the cases solved by your own procedure also stay in the company when the people who solved them move on.
Data stays in the EU, never used to train AI models: Security & Architecture.
Questions about your method
Can SolveR follow our own procedure instead of standard 8D?
Yes, once we build it as your method. You send the procedure and your report template, we build the steps in SolveR, trial the method on one of your cases and then go live.
Can the report come out in the format our customer requires?
Yes, SolveR builds reports in your templates. You send the report template your customer requires in the first step, together with the procedure.
What do you need from us to start?
The procedure your team works by today, your report template and one real case for the trial.
Does your method use the same knowledge base as 8D and PDCA?
Yes. The closed cases of your method go into the same knowledge base as the cases of every other method. When someone describes a similar problem, SolveR also shows cases from your method, and the other way round.
Standard methods
Every team picks the method that fits the problem, and one knowledge base stands behind all of them.
Bring your procedure and your report template to the call.