Software for the finest computer – The Mind


Posted by Tim Bryce on January 8, 2010

I went looking for a word in the dictionary and couldn’t seem to find what I wanted. Consequently, I invented my own, “brycetitized,” to describe a common situation we all experience from time to time, particularly in the workplace. Let me explain…

We all know there are right ways and wrong ways for doing things, such as designing a new building or bridge, producing a new model automobile, preparing a full course dinner, designing a major information system, or whatever. There are certain steps that must be followed in a precise order to achieve the desired end result. For example, when constructing a building, you must first layout the site plan before you pour the foundation, before you assemble the superstructure, before you put on the roof, etc. If the work is performed in the wrong sequence, disaster will naturally occur.

Sometimes we’re lazy and elect to cut a few corners as we know the correct process may take too long or is perceived as too laborious. This is called taking a “calculated risk” and sometimes we get lucky, but most of the time we fall flat on our faces. We know what the correct process is, but we just don’t want to follow it.

We even go so far as to invent new processes to execute the work which is perceived as a radical departure from the correct way, but only achieving mixed results at best. These new processes attract considerable attention and start a trend in the industry which others try to emulate. Even though people know what the correct process is, they elect to overlook it in favor of the new fashionable approach, which brings me to the necessity of a new word to describe this phenomenon. Consequently, I introduce you to…


bryce-ti-tizetr.v. bryce-ti-tized, bryce-ti-tiz-ing, bryce-ti-tizes
To overlook a correct course of action to take because it is not currently in vogue.
bryce-ti-tizer n.

“Smith bryceticized the company’s methodology in favor of his own agile process which failed and cost him his job.”

You’ll have to forgive the vanity of using my name as part of it, but I have observed this situation on too many occasions in the information systems industry alone. Analysts and programmers commonly forego the important planning and design stages of a project in order to rush to programming. This is like having a group of carpenters trying to build a building without a set of blueprints. They may possess some powerful tools and techniques to do the work, but without a clear understanding of what is to be built, and the proper steps to perform the work, they will inevitably produce junk.

Just remember, it’s “Ready, aim, fire.” Any other sequence will be counterproductive.

Keep the Faith!

Note: All trademarks both marked and unmarked belong to their respective companies.

Tim Bryce is the Managing Director of M. Bryce & Associates (MBA) of Palm Harbor, Florida and has over 30 years of experience in the management consulting field. He can be reached at

For Tim’s columns, see:

Copyright © 2010 by Tim Bryce. All rights reserved.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: