Databases Reference
In-Depth Information
The higher up the management chain, the more intimidating. Ultimately,
senior executives can be very intimidating. Executives absorb information
quickly and form opinions quickly too. They have the ability to immediately
hone in on any areas where there is uncertainty and doubt. Good executives
also have the ability to listen with an open mind, and are willing to modify
their strategy based upon new information. Therefore, if you are a member of
the business community, be mindful of how you might be perceived and act
as a partner. If you are a member of the IT community, remember these are
your partners and act accordingly.
Why take the time to reflect on this? Too often we fall into behavior patterns
of dealing with our peers or others within our own area of the business. As we
interact with those outside of our realm, we each need to take our audience
into consideration. This includes limiting the use of acronyms and jargon in
our discussions. Systems people are often criticized for excessive use of jargon.
Business people are just as guilty. This can be as simple as using industry
terminology such as market share, margin calls, or loss ratios. It may be
using abbreviations for projects and initiatives that are underway within your
organization. If these initiatives do not involve major systems development,
the technical staff may not know anything about them. Both business and IT
have to understand the success factors of the project and develop a common
level of understanding to achieve them.
Yes, that does mean the systems staff should learn the business basics,
including terminology and fundamental functions or processes. If the technical
project team members are struggling with understanding the business, you,
their business partner, can help! Recommend internal education classes for
them to attend. Often, introductory seminars are offered to new business
employees. Sometimes these are offered as online self-paced studies. Arrange
for the technical team members to participate. Compile a list of good topics
that lay out the principles of your industry. Consider the textbooks that you
used in college if the information is still current. Encourage the systems staff to
purchase these topics or loan them out if your department already has them.
Recommend periodicals that are targeted to each functional area, and don't
overlook online sources of information such as articles and blogs.
It is hoped that the systems people you are working with will be open to your
recommendations. The goal is not to turn the technical staff into full-fledged
brand managers, brokers, or accountants, but to give them a good background
about what you do. This process will go a long way in establishing a common
understanding between you and the IT partners as you seek to solve the
business problem.
There are several different partnership roles that need to be filled by
representatives from the business community. While each has a different level
of responsibility and time commitment, each is important to the overall success
