Comments on: Creating a new intranet: funnelling down to a solution http://www.steptwo.com.au/columntwo/creating-a-new-intranet-funnelling-down-to-a-solution/ News and opinion on all things intranet & CM Tue, 07 Feb 2012 04:15:20 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Recommended Reading for Intranet Professionals - somewhen End of 2008 ;-) at Intranet Matters http://www.steptwo.com.au/columntwo/creating-a-new-intranet-funnelling-down-to-a-solution/comment-page-1/#comment-585 Recommended Reading for Intranet Professionals - somewhen End of 2008 ;-) at Intranet Matters Fri, 09 Jan 2009 12:53:46 +0000 http://www.steptwo.com.au/columntwo/?p=3061#comment-585 [...] Creating a new intranet: funnelling down to a solution We start with a vague idea: “hey, let’s have an intranet!”. With no clear picture of what that means, our goal is now to “funnel” down to a concrete project plan. At each step, our activities should refine down what we are doing (and why). [...] [...] Creating a new intranet: funnelling down to a solution We start with a vague idea: “hey, let’s have an intranet!”. With no clear picture of what that means, our goal is now to “funnel” down to a concrete project plan. At each step, our activities should refine down what we are doing (and why). [...]

]]> By: James Robertson http://www.steptwo.com.au/columntwo/creating-a-new-intranet-funnelling-down-to-a-solution/comment-page-1/#comment-384 James Robertson Mon, 17 Nov 2008 03:04:01 +0000 http://www.steptwo.com.au/columntwo/?p=3061#comment-384 But this is a scoping and project planning issue! Intranet teams should not be committing themselves to delivering a piece of work that they don't know enough about. Once a high level scope has been determined, a piece of proper planning and research is done to nail down exactly what will be delivered (and how). Only then is there enough information to start the project. But this is a scoping and project planning issue!

Intranet teams should not be committing themselves to delivering a piece of work that they don’t know enough about.

Once a high level scope has been determined, a piece of proper planning and research is done to nail down exactly what will be delivered (and how). Only then is there enough information to start the project.

]]> By: PM Hut http://www.steptwo.com.au/columntwo/creating-a-new-intranet-funnelling-down-to-a-solution/comment-page-1/#comment-380 PM Hut Sun, 16 Nov 2008 20:45:11 +0000 http://www.steptwo.com.au/columntwo/?p=3061#comment-380 This is a nice, optimistic view of the projects, but a bit oversimplistic in my my opinion. The few hiccups in the Implementation phase are generally not so few, especially when it comes to a department not disclosing all its needs (and that happens a lot). This is a nice, optimistic view of the projects, but a bit oversimplistic in my my opinion. The few hiccups in the Implementation phase are generally not so few, especially when it comes to a department not disclosing all its needs (and that happens a lot).

]]> By: James Robertson http://www.steptwo.com.au/columntwo/creating-a-new-intranet-funnelling-down-to-a-solution/comment-page-1/#comment-327 James Robertson Thu, 06 Nov 2008 20:32:26 +0000 http://www.steptwo.com.au/columntwo/?p=3061#comment-327 Part of the 6x2 methodology is to give the intranet a version number. The first release is therefore version 1.0, six months later you release 1.1, etc. You can then say: "In version 1.1, we are delivering a search engine, photos in the staff directory, and a dozen key online forms." "In version 1.2, we will integrate the HR system to give seamless leave applications and online payslips. We will also expand the front page news." Each release should stand on it's own two feet, with enough benefits to justify the extra effort (and cost). Simply giving a version number helps the intranet team and organisation break out of the "maintaining the thing" mindset... Part of the 6×2 methodology is to give the intranet a version number.

The first release is therefore version 1.0, six months later you release 1.1, etc. You can then say:

“In version 1.1, we are delivering a search engine, photos in the staff directory, and a dozen key online forms.”

“In version 1.2, we will integrate the HR system to give seamless leave applications and online payslips. We will also expand the front page news.”

Each release should stand on it’s own two feet, with enough benefits to justify the extra effort (and cost).

Simply giving a version number helps the intranet team and organisation break out of the “maintaining the thing” mindset…

]]> By: Michael Hafner http://www.steptwo.com.au/columntwo/creating-a-new-intranet-funnelling-down-to-a-solution/comment-page-1/#comment-326 Michael Hafner Thu, 06 Nov 2008 14:21:06 +0000 http://www.steptwo.com.au/columntwo/?p=3061#comment-326 I like the plan and the steps; actually they just describe what happens anyway - regardless if you understand it or not. One problem I see is in how to keep the 6 months cycles alive. How do you actually keen them on the decisionmakers radar in order to avoid the expectation that it should be finally done by now...? I like the plan and the steps; actually they just describe what happens anyway – regardless if you understand it or not.

One problem I see is in how to keep the 6 months cycles alive. How do you actually keen them on the decisionmakers radar in order to avoid the expectation that it should be finally done by now…?

]]>