Biting the Binary Tongue

mp900262237-1-e1360282988795“Temple, why not write a blog for Trident?” They said.

“Anything in particular you would like me to write about?” I asked. “Whatever you would like.” They replied.

Where do I start? Naturally, when a solution eludes me, I turn to the foremost authority on the universe and its mysterious workings. Yep, I “Googled” it. It turns out that many seasoned authors like to tell aspiring authors to “write what you know!”

Awesome! Binary, bits, bytes, and nibbles (No … really … nibble: a collection of four bits). My inner geek squealed like a four year old girl on Christmas morning. I immediately sat down and wrote a very long-winded diatribe on the intricacies of recursive foreign keys and referential integrity constraints in a relational database. With a flourish of great pride and beaming accomplishment, I showed the work of art to my husband to proofread.

He fell asleep. It was 8 in the morning and he’d had two cups of coffee. Could my literary debut really be so boring? Was there “an English translation to my ‘gobbledygook’” as he put it? And then it occurred to me that he was from the planet Neptune and that I was really just dreaming. It was just like my mama always said, “To iterate is human, to recurse divine.” Ok, so that was L. Peter Deutsch, but come on – when am I ever going to get to bring that one out in idle conversation?

Still, there is something to be said for bridging that communication gap between an unnecessary technical explanation and just using layman’s terms. Just because you can say it, doesn’t mean you should. Many times over I face this issue with life in general.

My husband: “Hand me that two-eighteenths dual posi-algowrench lockometer.” (Yes, that is what it sounds like inside my head!)

Me: “You mean this silver thing with the blue loopy doo-dad at the end?”

Needless to say, when I came to work here at Trident Contract Management, I was completely blown away by the communication style amongst the staff. It doesn’t matter if you are in sales, development, or accounting. You could be an analyst or a consultant. The natural flowing language style is not threatening, or overbearing. It’s all about efficiency levels and respect. There is no need to under-simplify or over-techni-cate (my new word for the week). They are all about getting it right.

But every now and then I find myself biting the binary tongue and rethinking a sentence, but it’s a learning process and it takes time. Or, failing that, I might just “reverse the polarity of the neutron flow.” I don’t know yet. It’s up in the air.

Contract Management – It’s Personal (and should be)

mp9004385851-e1360190007344After 10+ years of helping our clients with their contract management efforts it still amazes me how personal contract management is to each organization and each stakeholder. Even the term “contract management” is personal. It can mean notification reminders and reports, document management, asset management, metadata management (all the details about the contract), process management, vendor management, a combination of these concepts, or something entirely different.The bottom line is that people want “contract management” to solve something that is personal to them (regardless of the initial need).

For most people “something” usually starts with a big picture organizational mandate (we need to reduce operational spend by 10%, comply with a new regulation, or report details to a new boss).The message and need can be clear but the breakdown occurs when those responsible for doing the work are already stretched thin, don’t have the tools/processes, or can’t get the people within the organization to consistently respond to their requests. So what do people do? They personalize the initial mandate to make it work for them.

The reason for this blog is not to state the obvious. It is intended to get people thinking about what an ideal solution for their environment would look like before they start the vendor vetting process.  If you have a foggy idea of what you want then vendors will be driving your needs to what they do best.  Put in the time to whiteboard the picture of what will solve the initial mandate and help those doing the work.

Here are some non-industry specific  examples of the types of review and desired functionality:

1.  Types of Contract Review (who are the stakeholders and what benefits do they want)

  • Legal Review
  • Financial Review
  • Risk/Compliance Review
  • Needs/Requirements Review (operationally does this contract solve our needs)

2.  Objectives/Functionality

  • Single shared repository with varied permissions
  • Document version control, review tools, indexing and search capabilities, audit trails, collaboration, and the ability to create new contracts
  • Document routing for approvals, review, comments, signature, and filing
  • Metadata about each contract (extracting useful information from the legalese)
  • Tracking and Email notifications
  • Dashboards and reporting

Feel free to connect with Trident (tsteiner@www.trident-it.com or 608-276-1909) if you need help figuring out where to start or defining what you want.  There are lots of options available to you. Making it personal will produce your best results!