(February 10, 2006) -   Decidedly not a sexy subject, software development is at the root of much of our daily anguish. From browser and operating system crashes to functionality that seems illogically absent from our key enterprise tools, we brush against the software designer's work in many aspects of our lives. Like many innovations that have come before, software design, as usually practiced, is outmoded. The next generation of tools has yet to be invented.

Before you nod right into your cup of coffee, rest assured that this topic is important to the daily work of making a Recruiting Operation run. Most Recruiting Software available today offers all the creature comforts of one-size-fits-all clothing. The flaw has every bit as much to do with the way that software design is practiced as anything else a vendor does. It's simply not possible to produce the level of customization desired by customers while making a profit.

Traditional software design uses a detailed "Requirements Development/Analysis Process". In other words, a variety of means (from user interviews and workflow analysis to behavioral observation) are used to generate a list of the stuff the software 'should' do (requirements). The list of stuff is then prioritized, reviewed and approved. The highest priority things get done first. What can be specified can be automated.

The routine processes in knowledge work are often low value but easy to automate. Because these transactions happen frequently, the contemporary software design process overemphasizes their importance. We call it "Knowledge Work" because the critical aspect of what gets done involves judgment, not repetition. The most important things are the exceptions rather than the norm.

There is not, to our knowledge, an analysis process that observes work being done in order to identify the highest value components of the job. Current Software Design practice takes a snapshot and automates the things that happen frequently. In the long run this leads to automated processes that reinforce mediocrity and make a bad system hard to change.

Very few people are even exploring the idea that the Requirements Development Process is the culprit behind broad dissatisfaction with software products. In manufacturing, the idea of mass-customization is the replacement for pure assembly line thinking. We used the assembly line idea until it wore out in the early 80s.

The next generation of Software Design will be more like mass-customization. But, it will simultaneously use probability theory to predict which Requirements might be the most important and then have a mechanism to verify the value of things that are automated.

Until there is a new way of thinking about software, vendors are stuck with the old one. If you are investing in a Recruiting platform, be sure to understand clearly how the vendor develops its requirements. We don't think that any solution will be deeply satisfying but some will be far superior to the others.

John Sumser

---

Home | ERN | Bugler | The Blogs | Blogroll | Advertise | Archives | Careers

---

Contacting Us:
interbiznet, Mill Valley, CA 94941
415.377.2255
colleen@interbiznet.com

Copyright © 2013 interbiznet. All rights reserved.
Materials written by John Sumser © TwoColorHat. All Rights Reserved.

To receive this Newsletter in Email each weekday, please use the form on the linked page.
If you have any problem with this form please click on the link below and enter your email address:    SUBSCRIBE      Thank you.