|
THE
FIN DE SIEGLE LEGACY MINDSET
By
Ronald G. Ross, November
1999
A
consultant recently told me about an incident at his client's. I'm sure it's
one repeated around the world many times every day.
A
group of developers were developing a new web-based application to support
bread-and-butter interaction with customers. They were very into the coding.
The consultant recommended that they write down the business rules they were
implementing. Their puzzled response was "Why?". After a minute or
two of dead silence, one of the developers cautiously added, "We can
always just go back and ask the business users again if we need to."
Can
you always just go back and ask the business people for the business rules
again? Well, actually yes - at least once or twice usually. But in my
experience, their enthusiasm and confidence level in you are going to fall off
rapidly after that. Why shouldn't it? You obviously just don't seem to be
"getting" it. (And that will be true even if they're not really
"giving" it very well, which happens pretty often too.) There's such
a simple solution - all you have to do is write 'em down as you go.
Now
remember, this was a web-based application. As the consultant went on to point
out to them, the goal was to dis-intermediate - in other words, to remove the
middlemen. In this case that meant the company representatives who had been
supporting the customers up until now. Once those representatives are gone
from the scene, then who will you go back to with questions about the business
rules?
This
drew more blank stares from the developers. Their job was to develop, to code,
to build, to get it running - not to worry about what might happen years from
now. The consultant pointed out that changes in business rules is no longer a
matter of years these days, but of weeks, days or even hours. More blank
stares.
The
consultant and I chuckled over this (more like amused groans). Here were
developers who could conceive of complete business transactions with customers
worldwide in a matter of seconds, truly revolutionizing commerce. Yet these
same very creative people were unable to grasp that the rules of this game
would almost certainly change within a matter of months, if not weeks or days
- and that you need to do something about that too.
I
guess the bottom line - I'll leave you with this thought for Y2K - is this.
You can shrink the legacy mindset, but you may never be able to get rid of it
completely.
©
1999, Ronald G. Ross.
|
|
September 2005
The Fin de Siegle Legacy Mindset
By Ronald G. Ross -- (November/December 1999)
August 2005
Analysis Paralysis Just May Save Your Life
By Ronald G. Ross -- (September/October 1999)
July 2005
If We Had Started Coding Already...
By Ronald G. Ross -- (July/August 1999)
June 2005
Your Core Business Processes Need a Rule Engine
By Ronald G. Ross -- (May/June 1999)
May 2005
Four Things Wrong with the Way We Develop Information Systems
By Ronald G. Ross -- (January/February 1999)
April 2005
Push-Type Data Hub vs. Pull-Type Data Warehouse
By Ronald G. Ross -- (November/December 1998)
March 2005
What Knowledge Management is About (And What it Has To Do With Business Rules)
By Ronald G. Ross -- (September/October 1998)
February 2005
The Next Great Leap Forward ~ About the Changes You See
By Ronald G. Ross -- (May/June 1998)
January 2005
Business Rules as Customer Interface
By Ronald G. Ross -- (March/April 1998)
December 2004
Components and Business Rules: Do They Connect?
By Ronald G. Ross -- (January/February 1998)
November 2004
The Policy Charter: A Small-Sized Picture of the Big Picture
By Ronald G. Ross -- (November/December 1997)
September
2004
Implementing
Application Packages: Is There A Better Way?
By
Ronald G. Ross -- (September/October 1997)
August
2004
'Why'
is Why Business Rule Methodology is Different
By
Ronald G. Ross -- (July/August 1997)
July
2004
Never-ending
On-the-Job Training
By
Ronald G. Ross -- (May/June 1997)
June
2004
Re-Usability
in the Business Rule Approach
By
Ronald G. Ross -- (September/October 1996)
May
2004
The
Newest Idea In Business Rules: Rules Normalize!
By
Ronald G. Ross -- (March/April 1996)
April
2004
An
Open Letter to DBMS Vendors: We Need Active Database Systems
By
Ronald G. Ross -- (January/February 1996))
March
2004
The
Greatest Irony Of The Information Age: Business Rules
By
Ronald G. Ross -- (May/June 1995)
December
2003
Business
Rules:
Knowledge For Knowledge Workers
By
Ronald G. Ross -- (November/December 1995)
November
2003
"Play
Ball!"
By
Ronald G. Ross -- (March/April 1994)
October
2003
Enterprise
Architecture: Issues, Ingibitors, and Incentives
By
John A. Zachman -- (November/December 1999 & January/February 2000)
September
2003
Packages
Don't Let You Off The Hook
By
John A. Zachman -- (July.August & September/October 1999)
August
2003
The
History Of Steam-Powered Ships
By
Ronald G. Ross -- (November/December 1988)
July
2003
Life
Is a Series of Trade-Offs and Change Is Accelerating!
By
John A. Zachman -- (January/February & March/April 1999)
June
2003
"Business
Rules, At What Cost?"
By
Ronald G. Ross -- (January/February 1994)
May
2003
"Yes
Virginia, There IS an Enterprise
Architecture"
By
John A Zachman -- (November/December 1998)
April
2003
Business
Rules: Birth of a Movement
By
Ronald G. Ross -- (May/June 1994)
March
2003
Business
Systems And Information Support Systems
By
John Hall -- (January/February 2000)
January
2003
Enterprise
Architecture: Looking Back and
Looking Ahead
By
John A. Zachman -- (July/August 1998)
December
2002
Why
I Like the Zachman Framework Architecture"
By
Ronald G. Ross -- (July/August 1991)
November
2002
The
Framework for Enterprise Architecture (The 'Zachman Framework') and the Search
for the Owner's View of Business Rules
By
John
A. Zachman -- (January/February 1998)
October
2002
Business
Process Re-Engineering
By
Ronald
G. Ross -- (March/April 1997)
|