Home/DriveWorks guides/How to choose your first DriveWorks project

How to choose your first DriveWorks project

Pick a first DriveWorks project that is simple, independent of other projects and systems, and used by the most people. A quick, visible win brings more of the company along than an ambitious configurator that ships a year later.

The formula

At Base 10 the same story comes up over and over: "We have this new software and it can do all this stuff, but where should we begin?" The answer is a short formula.

Simple + Independent + Most Users

Simple

Get the quick win. A year from now you will look back at your first project and cringe at how it was built. If it was simple, it will also be quick to rewrite. If it was the flagship product line with every option, you will be living with those early decisions for years.

Independent

Every connection to another DriveWorks project or another business system makes the project harder to build, harder to debug, and harder to maintain as those systems change. Integration is where the big gains are later. It is the wrong place to learn the tool.

Most users

Start the first release with a small group of power users so the feedback is good. But choose a project that will eventually touch a lot of people. The more people who know what the company can now do, the better.

Why "most users" matters more than it looks

A project that helps many people does something a technically impressive one cannot: it recruits. People see their own work get easier and start asking what else could be automated. Opportunities that were invisible surface because people are finally being asked how their job could be better.

That is the shift from a work-harder culture to a work-smarter one. It also makes the organization less averse to change. Pair it with competent users in key parts of the business and you will soon have more feature requests and project ideas than you can build, which is the problem you want.

What that looks like in practice

Good first projects are often not the product configurator at all:

  • A "next number" tool. Replace the shared spreadsheet that hands out part, drawing, or customer numbers. Everyone uses it, it has few rules, and it removes a daily irritation.
  • One simple product family. The one with the fewest options and the most repeat orders, not the one that hurts most.
  • A single document. The quote, the pick list, or the tag that someone retypes for every job.

Poor first projects have the opposite profile: the most complex product, a hard dependency on the ERP from day one, and one user.

Is it worth automating at all?

A quick test before starting:

  1. How long does the task take, and how often is it done?
  2. How much of that time would automation save?
  3. Does the saving, over a sensible period, exceed the time it takes to build?

Do not over-analyze the ranking. If several candidates pass, pick one with your gut and start. Savings applied today pay back sooner than better savings applied next quarter.

Ship it before it is finished

Engineers are trained to get the whole design right before metal is cut, because rework is expensive. Software rewards the reverse. Get something simple and useful in front of people, then improve it with their feedback. A first DriveWorks project held back until it covers every case usually never ships.

If you have recently bought DriveWorks and are stuck on where to begin, or you have reached a plateau and want to make the next jump, that is what Base 10 does.

Common questions

What should our first DriveWorks project be?

Something simple, independent of other projects and business systems, and useful to many people. A small tool everyone uses is a better first project than the most complex product line.

Should the first DriveWorks project integrate with our ERP?

Usually not. Each connection to another system makes a project harder to build, debug, and maintain. Prove the tool on something independent first, then add integration, which is where the larger gains are.

How big should a first DriveWorks project be?

Small enough to release quickly and rewrite without regret. A first project teaches you how you should have built it, so keeping it small keeps that lesson cheap.

How many people should use the first release?

Release first to a few power users for good feedback, but choose a project that will reach many people. Wide visibility is what builds support for the next project.

Base 10 Consultants is a DriveWorks Authorized Services Partner: CPQ configurators, design automation, and CAD-to-ERP integration for manufacturers.

Book a 30-minute call

Base 10 Consultants is a DriveWorks Authorized Services Partner and an independent company. This page is not written, reviewed, or endorsed by DriveWorks Ltd. DriveWorks is a trademark of DriveWorks Ltd; SOLIDWORKS is a trademark of Dassault Systèmes SolidWorks Corp. Behavior described here can differ between versions, so check the DriveWorks documentation for the version you run.