In 2005, the read-writable web, software as a service (SaaS), blogs, wikis and RSS feeds were fairly new. I started a blog on Information Management which tied neatly with my lifelong interests. I summarized my blog theme as follows:
So much stuff on information management, content management, information technology, data management, records management, library management... But how does it all come together? Where to find an "information management body of knowledge"? (IMBOK)
The blog was titled Information Management Now. It is still online. The IMBOK reference was an implicit analogy to the Project Management Body of Knowledge (PMBOK) developed by the Project Management Institute (PMI). Aspiring project managers could turn to PMI to learn the PMBOK and obtain their PMP certification, whereas practitioners in Information Management had no equivalent certification or body of knowledge to turn to if they wanted to develop ownership and leadership of the larger Information Management ("IM") discipline. This larger discipline was intuitively seen at the time as larger than Records Management, Data Management, Information Technology, Library Management, etc..
It is in this context that I founded at the time the Government 2.0 Think Tank ("G2TT") Association. G2TT had executives and IM practitioners drawn from many federal Departments and Agencies and were inspired to move the dial forward from Government 1.0 to Government 2.0. Despite a promising debut, this movement forward came to a screeching halt. The story of the rise and fall of G2TT is documented in this 2008 IT World Canada story. In the same period, I also founded the Ottawa Drupal Group - I am glad this community is still thriving many years after my departure from Ottawa.
Fast forward to 2017. I am resuming an online presence after more than ten years of absence. In doing so, I thought it would be fitting to bridge the old with the new so I curated my old blog and imported the few following posts from the old blog:
- Inaugural Post - Information Management Now. Title says it all!
- What is Integrated Information Management. 12 years later, I would not change much to this definition of integrated information management. However, integrated information management is not the same thing as digital transformation. But that is the topic of another day...
- Googlezon and EPIC. This was a prophetic video if there was ever one. The accuracy of predictions (in the general sense) is astonishing.
- On Wikis and Letting Go. I read a lot of commentary in 2017 about digital disruption, how we are trying to digitally disrupt how government is operating... We were not using these words in 2005, but we certainly were digitally disrupting, albeit "intragovernmentally".
- Is Web 2.0 Too Farsighted for Governments? More digital disruption, 2005 flavor.
- Why Web 2.0 Matters. President of the Treasury Board Honorable Reg Alcock quoted as lamenting the process of requirements definition and procurement in the federal government. Hopefully, in 2017, we can accelerate the widespread adoption of agile development!
- Information Management as a Unified Discipline. My assumption at the time: The commoditization of IT, the increasing pressure to achieve better cost-efficiency and higher management expectations are forcing IM to reorganize itself into a coherent field of practice. IM is becoming more “unified” or “integrated”.
- Knowledge Management as Another Discipline. There were sometimes Knowledge Management (KM) and Information Management (IM) confusion at the time, so I wrote briefly on topic.
- The Relationship Between Business and IT. This is a fun post - if you are into that sort of humor. It illustrates the tension that existed at the time between the IM and IT functions in government. I am told this tension still exists...
- Solving Corporate Email Overload - with blogs. This post shows an example how 2005 modernization could be simple.
- Government 2.0 Think Tank at BarCamp Ottawa. In 2017, at FWD50 for example, lots of buzz on how it is necessary to connect with people "making it happen" and to be collaborative. I agree. That was the spirit in which BarCamp events were organized over ten years ago.
- Government of Canada IM Day 2006 | Web 2.0 "Track". This post gives an idea what kind of discussions were federal government modernization proponents engaged in when planning a "Government of Canada IM Day".
- Why Drupal Would Make Sense in the Government of Canada. Free and open source Web Content Management Systems (WCMS) were looked at suspiciously at best in government in 2005. I offered 11 reasons for adoption. Drupal remains to this day one of the most popular and effective WCMS, supported by a vibrant and active developer community worldwide.
- Why Defining Requirements is Not Good Enough. On 28 May 2006, I wrote: "The generally accepted approach in software development now calls for iterative (or evolutive) development. You figure out what you need, then you build some. By building some, you can better articulate further requirements. The cycle continues." Amazing that in 2017, agile development is still considered to be a novel method in many government circles...
Hope you enjoyed the selection of these past posts. Now, onward to the future and digital transformation!