Mega monster or Many monsters? (Fully integrated or Best of Breed)

I don't think I can count the number of times that I have had a conversation about software that spirals into a conversation of "we need fully integrated" versus "need the best features." This is the conversation that I have always talked about as a single database (fully integrated software) versus best of breed. Best of Breed to me means you pick the best software for each of your distinct business areas then you work to integrate them or build connections to share data.

However, this conversation has always focused on the features of the software. This article from the NTEN:Change magazine has really got me thinking about it from a different perspective, a constituent data perspective.

Data is all the rage again now that APIs are common, visual dashboards run amuck, information rules and everyone needs more numbers to build those cool infographics that we all love (to hate) (but can't stop looking at).

Anyway, here is the thought:

You think through the different types of constituents you will track and interact with, how you will need to use the data and how interrelated they are.  Here is an image that they use to help describe this.

But dont take my word for it, Go read the article from NTEN and then be sure to subscribe to NTEN:Change, the visuals are striking, but I look at it for the articles. They are always fantastic. And if you are looking for a way to convince your CEO or executive staff about the value of tech, subscribe to NTEN:Change for them. They will wonder where the emails come from but they will thank you for the wonderful information.

Tool Trends or People Trends? (Part 8 of 11 on Managing Tech 2 Meet Mission)

"Where should you focus your efforts to find out where your stakeholders are and what they are doing online with and for your organization."

"What data is meaningful?"

"What is trend, and what is simply trendy?"






I was reading this book to get answers not more questions. But Michael Cervino decides to start his Chapter in the NTEN with questions. And not just questions, but questions that I dont hear my organization asking themselves.  It is like Dr Seuss once said "One Tweet, two tweet, red tweet, blue tweet." Oh no that isnt the right quote. Sorry, it is like Dr Seuss once said "Sometimes the questions are complicated and the answers are simple."

I am not exactly sure what the quote from Dr. Seuss means, but here is my interpretation. Sometimes it is harder to find the right question to be asking than to find the answer.  The question isnt "should we have a facebook page?", it could be "what is our goal in communicating online?" The question isnt "how do we fundraise on Twitter?", it could be is "where are our potential donors online?"

RFPs (Requests for Proposals) are a great example of making sure to ask the right question. If you ask a vendor, "can your product handle multiple integrations?" They will answer yes. But what does that question even mean? And of course they say yes, because anything can be done with extra customization, you didnt ask if it exists now, you just said can it...

I learned a lot in this chapter. Michael does a great job of outlining how to create SMART objectives, gather data, analyze data and identifying trends in order to understand your constituents better. Michael keeps all of this online activity in perspective by focusing on the organizations goals and then find the correct audience match.  This should not be about the tools or the trends in technology, rather it is tracking your audience and their engagement with you.

But the questions and the tracking cant just happen at the beginning of the online presence rollout. Back to the RFP example, how many times do we actually go back a year later after we select the vendor and compare the progress to what the vendor said we would have in the RFP? Or do we simply forget the questions we asked and only examine the current reality? You dont have to continually ask new questions, sometimes it is best to go back and ask the same question again to see if you did answer it or if it was the right question.

I have picked up on one thing from Judith here at work as a part of our online registration system rollout.  And that is to document the questions and decisions that have to be made, then include the answer (with the reasoning). Because inevitably someone will ask the question again or will change their mind.  This isnt about just saying, told you so or saying we already did that. It is to avoid asking the wrong questions and making the same mistakes.

Anyway, nicely done chapter Michael!

Over 11 weeks I am doing a themed series of blog posts. Each week I will write about a chapter of the book called Managing Technology to meet your Mission. This week is on the 8th chapter by By Michael Cervino called Where are your stakeholders and what are they doing online? You should totally buy the book. (In case you are wondering, I am volunteering to do this, I am not getting paid or in any other way reimbursed for this. I just love NTEN and their events.)

Flickr photos by Travelin' Librarian and by Thomas Hawk