Daily Archives: February 28, 2016

Interesting to Compelling


20160225_ReynoldsHomePageOld

I didn’t realize it at the time but from the moment I started as a trainee software developer with Reynolds & Reynolds (now Pentana Solutions) in October 1988, I was introduced to three very important concepts in business and in particular, creating software products to add value and make the business (and the businesses using them) money.

The first is the concept of defining the value you provide to your clients. It wasn’t until many years later that I learnt this as the process of taking something from “interesting to compelling” and once you could achieve this transformation, great things would follow. The second concept is finding the commercial point of a product in the development process because that is the point when it needs to be taken to your client base, not when the development is finished. The third concept was creating barriers to exit for your clients; products, processes or services within your offering that the client can’t do without (real or perceived).

Reynolds & Reynolds Australia (R&R) supplied dealer management systems (DMS) to car dealers and was a wholly owned subsidiary of The Reynolds & Reynolds Company (R&R US) based in Dayton, Ohio. It had been marketing/selling a solid, rudimentary DMS that was interesting for dealers as it offered value as a DMS but was one of a few in the market with similar capabilities and as such there was no clear leader at that time.

R&R knew that to dominate the market he had to move from having an interesting offering for dealers to a compelling one. Being interesting meant you would be shopped against other interesting offerings from your competitors and the best price would win. Being compelling meant your client just had to have what you have to offer; or accept something sub-standard and adapt. This then gave you something your clients would pay good money for and that something was value.

The ERA DMS was introduced to US dealers by R&R US in 1987 and promised to be a game changer as it was the first on the market to seamlessly integrate the various parts of a car dealership within the computer system: accounting, new vehicles, used vehicles, spare parts, service, aftermarket, etc. ERA had to be brought to Australia.

I was hired as a trainee computer programmer tasked with “Australianizing” ERA as fast as we could in a small team (change operating systems, convert dates, miles/kms, etc and change some dealers process within the DMS). The project was top secret within R&R and it had created a buzz around the office. R&R US sent out a couple of programmers to help us along early on. For six solid months we trawled through hundreds of thousands of lines of code making change after change, compiling the source code and making sure each program worked after the changes. For me it was a buzz learning a new programming language on the job, although at the time I didn’t realize exactly what we were working towards achieving. ERA was the product to take Dealer Management Systems in Australia from interesting to compelling. It was the product that would change the landscape for R&R.

Now that we had the first piece of the puzzle, unbeknownst to me, we needed to work out the second piece of the puzzle; finding the commercial point in the development process when ERA would be taken to the client base. I had no idea at the time that this was the process. Wouldn’t it be sold when everything was finished?

It was announced that the first dealer install of ERA would be in April 1989, a mere 6 months after the project began in earnest. I thought it was crazy as we still had so much to do (and we certainly did) but as I learnt later, the product was ready to create value for the client regardless of whether development was finished or not. A part of this lesson was that the development process is never finished so if we wait for that moment, we would never release anything to a client or we would release it too late. I think this is why so many technology minded programmers don’t understand the business side of technology and the ones that do prove to be very valuable.

There were many problems in the first installation. Software conversion issues, differences between Australia and US dealer process, operating system environment issues and so on but ultimately these were issues that we were going to have now or six months later when most thought we would be ready. Very quickly ERA starting providing value to the client and the right commercial point of the product had been found. Problems were being fixed on the fly both on site at the client and back in the R&R office. It was all hands on deck to make it right for the client.

ERA didn’t prove to be a very hard sell in a very competitive and tough environment of car dealers. Very quickly ERA helped R&R become the clear number one in Australia but really it wasn’t just the product that made this happen. Without the wisdom of the leaders at R&R in particular to make the investment to bring something compelling to Australia and the judgement to find its commercial point as early in the cycle as possible, a competitor might have stolen the march on R&R in releasing something more interesting that may have changed the landscape.

The third concept, creating barriers to exit, was the next step.