Adequate
How often do you settle for "adequate?" Not great, not bad, just "adequate."
There's a restaurant very close to Perimeter Church that I wish I wanted to go to all the time. It is close by, big tables, pretty good service, and sometimes they even have wireless. But, the food is only "ok." It's not bad...just nothing to get excited about.
As we've been working on our new Intranet plan, Scott Logan challenged me with "let's not settle for adequate." That's a great idea! But...what does it mean?
We've been working hard to use SharePoint. After all, it's the obvious "easy" answer. And...we've been tremendously underwhelmed. Talking to others, they've had a similar experience. SharePoint works, it can do all kinds of things, but it's not easy, and frankly, it's somewhat ugly! So..with a lot of work, we could have, yup, an "adequate" solution. Let's not settle for adequate.
We have a media archiving solution that is, um, adequate. We have an internal workflow system that's...adequate. We have a purchasing process that's..ok, you guess. How may other "adequate" systems do we have? Why don't we have excellent? Perhaps three reasons: 1) We don't know of excellent solutions. 2) If they existed, they'd probably be very expensive. 3) Most of the time, we wouldn't know excellent if it hit us in the face!
What do you have that's "adequate?" What would it take to get to excellent?






Recent Comments