Intranet diagnosis cards

Another free gift from Intranet Directions!

Last Christmas we enjoyed giving away our free cut-out-and-keep Intranet Tactics cards so much that we wanted to experience that warm glowing feeling again. So, in the same spirit of global intranet community-ness, here are our Intranet Diagnosis Cards.

Before you can work out where you are going, you need to work out where you are. Again, evoking the spirit of Brian Eno’s Oblique Strategies, we’ve created some cards which have some questions, some suggestions and some ever-so-slightly antagonistic statements on them. These are designed to get you thinking about what problems you, your intranet and your organisation may have. Is it the technology? Is it the users? Is the approach? Is it the coffee out of the vending machines? Do you even have any problems?

These cards can help get you in the zone for brainstorming areas of weakness and frustration with your intranet, and diagnosing the causes you’ll need to address. This is a first step towards a cure by playing some quick tactics or kicking off the whole strategic shebang. Conversely they’ll help you to consider your intranet successes – don’t be so hard on yourself.

Use the cards in an intranet team meeting, away day, or just occasionally visit for some fresh thinking. Or scrunch them up, set fire to them and wish you’d never downloaded them in the first place. It’s up to you.

As with the whole of Intranet Directions, this is a bit an experiment. We’d love to hear what you think, how you have (or haven’t used) the diagnosis cards. Enjoy.

Steve Bynghall and Chris Tubb, May 2014

Instructions for use

  1. icon_mis  Wake up one morning feeling like your intranet has so many problems you just don’t know where to start.
  2. icon_download Download the Intranet Directions Diagnosis Cards PDF (239 KB, on us, for free, no sign-ups)
  3. icon_print Print it out on real world paper. Or on some nice card with a view to getting it laminated if you have loads of time and budget. But you won’t have either
  4. .icon_papers  Take the pieces of paper from the printer, and go back to your desk.
  5. icon_cutting Get some real world scissors and cut across the dotted lines. Be careful with those scissors, now. You might want to get someone with a technical background to help.
  6. icons_cards  Place the cards in a nice neat pile and contemplate their zen like papery-ness. Grab some of your colleagues for a meeting.
  7. icon_cardsStart to think about some of those things the users and your team moan about.
  8. icon_look  Look at the cards to start to tease at exactly what the problem is. You can’t blame everything on the users or IT, you know. How about a few post-its?
  9. icon_idea Also identify some successes. Make small paper aeroplanes out of the ones that aren’t problems. Start to see some common themes emerging. Articulate the major pain points and prioritise what needs to be addressed.
  10. icon_happy  Feeling motivated, commit to making a plan of action.
  11. icon_drinkYou’ll now need a stiff drink after such brutal self-honesty. Raising a glass to the Intranet Directions team, you’re now on the path to success.


Download the Intranet Directions Diagnosis Cards PDF (13 pages, 230 KB, 52 cards, on us, for free, no sign-ups. We are nice people)

thumbnails for diagnosis cards

Never get solely fixated on driving intranet or ESN adoption

In Chris’ last post he outlined why it’s important not to confuse strategy with tactics when it comes to intranets. In my view one of the reasons for this is because intranet teams have a habit of focusing too much on the tactics and working energetically and diligently to make them work, without ensuring they are part of a strategy which ensures business value.  Ultimately this leaves teams open to a withering “that’s nice, but so what” from senior management.

One of the reasons for this is the obsession with driving adoption when it comes to intranets and collaboration platforms.  Of course if you build a site or post content, it’s only natural that you want more people to use it or read it. More visits to the homepage, more users registered to the social network, more collaboration sites created, more comments on the news items, more unique visitors. These are often the validation of an intranet team’s efforts and the evidence of success.  They are also some of the easiest things to measure.  I’ve become fixated on driving adoption in my work and I’m sure I will again and again.

I’m not going to pretend that adoption isn’t important, because it is. It may well be the prerequisite for the overall success of your intranet strategy. Perhaps you need some sort of scale to feel an effect an organisational level, for something to be transformative, or to realise some sort of ROI benefit.  But it’s only part of the mix and increasing adoption on your intranet is definitely not a strategy in its own right.  

Focus on value not adoption

Adoption also only has value if what users are adopting has value. It has little value in itself. For example email has spectacular adoption, but now a reduction in that adoption level is regarded as a good thing.

In his recent presentation at Congres Intranet in Utrecht  Lee Bryant is quoted as saying “We don’t need people to adopt the intranet. We need people to do their job.”  This is spot on. If an intranet has less value, perhaps because it is only an internal communications vehicle, then adoption becomes a little bit of a red herring. Yes, there may well be some residual value in many people visiting the homepage and reading the news, but does the impact really justify the efforts?

The lure of the uptick

It’s also really easy to be seduced by the uptick of adoption. There will be a post-launch surge which provides an immediate high for the project team after the energy-zapping pre-launch effort. But we all know things might not pan out so well in the medium to long term.

There can also be a degree of complicity in presenting the stats to stakeholders, showing a nice upward-looking trend which presents success at a glance.  And that’s not to say these adoption trends might be really significant and fantastic, but they might not be.

It’s that tactics-and-strategy-confusion thing again

When adoption becomes your main focus, you’re in danger of judging success on the delivery of the tactics which drive that adoption. Intranet teams do have a lot of tactics at their disposal to drive adoption. I’m thinking better usability, a nicer design, gamification, subtle nudge tactics, advocate networks, publishing communities, notifications, personalisation, customisation, dashboards, metric scores which reflect engagement and adoption, encouraging viral growth, even traditional change management. These can all be excellent and important techniques when done right, which do help drive those numbers up.

But what does a 20% increase in the number of visits to the homepage mean? What does the unexpectedly fast viral growth of a social network mean? What does a 25% rise in the use of Team Sites mean?  Intranet managers and ESN community managers with their eye on the ball need to ensure it means something for their organisation and the people who work there.

Chris says:

“Now. I bloody love metrics. But it isn’t blind love and I can see its flaws. Adoption is a lonely metric unless it is enriched with a bundle of other more meaningful business metrics that should include a measurement of what you were after in the first place. Adoption worship, I think, perhaps comes from a lack of a hard understanding what your benefits were up-front. If you are deploying an ESN to break down barriers between functions go and look for the cross functional diversity of different communities and measure that. If you want to break the cold and steely grip of email, go and look for a drop in the number of email attachments. I understand where people are coming from. When you’ve done a great big intranet project you want it to be loved, but each large project is poker-chips-down, and some of your bets won’t work and you won’t press through into the late majority for many reasons. Go and read Everett M Rogers’ “Diffusion of Innovations” for more on this.”

Don’t get intranet strategy and tactics confused

Your intranet strategy is a plan of action to ensure that you are prioritising what the business needs of you in the most appropriate way.

A tactic is one way of achieving your strategy.

Try not to get the two confused.

  • Improving search is not a strategy. It is a tactic that supports a strategy of maximising findability so that people can get the information they need.
  • Personalisation and customisation are not strategies. They are tactics that support a strategy of maximising relevance for the user and the publisher.
  • Mobile intranet is not a strategy. It is a tactic that supports a strategy of enterprise mobility to ensure that people can get what they need to get done, irrespective of their location.
  • SharePoint (good God!) is not a strategy. It is a tactic that supports, umm, replacing your end of life content management system perhaps or consolidating numbers and types of platforms. Whatevs. This is the case with any particular product name.
  • Social is not a strategy. It is a tactic that supports a strategy of getting people to collaborate and share in a certain way that will contribute to new ways of working.

Tactics can be used for lots of different strategies. For example you can use the implementation of a social platform to support employee engagement and involvement. Both good uses for a different reason. Tactics may be rather modest such as making sure you take your opposite number in IT or Communications to lunch once a month.

Why is this important? A strategy is based on the beneficial outcome of delivering a business need. If you dress up a tactic in strategic clothing you will be found wanting. A few simple questions by a senior manager and your hopes and dreams and reputation will be skewered. If you are unaware of this little game you might spend the next budget cycle muttering about chronic under-investment in intranets being to blame. No. It was you. You fluffed it. Sorry. And there is enough goodwill and interest in these tools out there to not make it a pure hard-cost problem. Find your allies and work with them.

Lastly there is no shame in not operating strategically. If it just you and a monkey delivering the intranet for 5000 close personal friends, just making it work is enough. Make it work well and you should get a medal. There are things that intranet should just do, and do well. Concentrate on those.  Your strategy is more personal: survival and getting out of such a pickle. I give you a hall pass on being required to speak business jargon unnecessarily.

Chris Tubb March 2014

Steve says:

“Chris is right. Confusing a tactic with a strategy is a dangerous game. First of all you potentially alienate the stakeholders and your users who can’t  quite share your enthusiasm for this initiative. Secondly it encourages narrow thinking.  So a limited mobile intranet is up and running, which is great, but your non-office based staff are shrugging their shoulders as they don’t have the BYOD policy,  the wi-fi needed in the factory facility, and the email accounts needed to truly work in a different way. Thirdly the tactic you are pursuing becomes the focus in itself, which means taking your eye off both the ball and the goal.  Always work with some sort of strategy, and slot your tactics in appropriately.”

Don’t let your project plan and governance, become your intranet strategy and governance (or why Intranet stakeholders are your BFFs)

A quick one, but worth repeating.

Your intranet is a complex array of browser based systems and services. They are tangled together like spaghetti alla crazy glue. Your users don’t really get the idea that one bit is owned by one team, and another bit is owned by a different team; nor should they care.

If it has been a bit of a mess the reason is usually that collectively the idea of the intranet has not been a strong one. One day there is enough embarrassment-in-common amongst the great-and-the-good that something-must-be-done. “We need a project to build a new intranet,” they say. A project manager is found. Requirements are gathered. The PM rounds up a strange breed of people called “Stakeholders”, who presumably know what they want. The project starts to fly and some structure is thrown over the rhubarb-muttering crowd like a hopeful fishing net. That net is called “Project Governance” and it attempts to bring some structure to the panicky madness that is a large scale IT development project.

After a bit of monkeying around with Gantt charts, test scripts and usability testing the intranet is handed over to the people that will put content in it and content is poured into it like beer into a tankard. Champagne corks are popped that everyone has a little party, and the PM rides off into the sunset. His work is done here. The development team go and work on something else.

The governance, of course, falls apart because the project is over. The stakeholders drift away. The intranet degrades, until the next time. Then people like Steve and me shuffle onto the scene. We ask if there is an intranet strategy. Small voice: “Not really. Just ideas you know…” Mumbling. Staring at shoes. Is there a steering group. “Used to have one…” Governance model? “Pfffft…. Wild-west, innit.”

There is a better way, people…

Of course what you really need to do is to sort out the strategy and governance to scope, define and set a roadmap for the future. The projects can then fall within this framework.  So…

1. Get a group of people together who are accountable and engaged about the intranet. They will want to use it to drive business outcomes with things like “efficiency”, “engagement” and “knowledge”.

2. Get them to figure out a vision and a plan for the whole intranet – from tip to tail, from the top of the tallest shiniest news story to the dark and dingy team sites. No site left behind.

3. Get them to assemble a way of everyone working together: a governance model that encompasses anything that people might conceive of as the intranet. Let it scale.

Then start creating projects to deliver a bit of the intranet vision. Any project you create should be part of an overarching plan to deliver your intranet strategy. Your intranet “project”, even if it is huge and transformational should be initiated and accountable to your intranet steering group.

There is a better way: PEOPLE

Your intranet isn’t SharePoint. It is a idea that brings unity and structure to people, places and things. Your vision, strategy and governance aren’t just documents. They are held in place by the people who are involved and invested in it. No people, no belief, no mandate, no strategy.

Il faut cultiver son jardin, dagnammit.

If you are in this horrific groundhog day of big-bang project, followed by cold-tea ambivalent mediocrity and eventual and inevitable failure, you can break the pattern.

Save and close that Word document, get up from your desk and go speak with your stakeholders. Bond with them. Give them a reason to believe in a cheery future and your intranet’s place in it. The belief starts with you, and when someone asks what platform your intranet runs on, point at your intranet steerco and say: “Those guys.”

Steve says:

Far too often intranet  strategy comes grinding to a halt for various reasons and then gets revisited when its big project time. The danger then is intranet governance and project governance overlap and become indistinguishable. Sure there are similarities – some of the same stakeholders  are almost guaranteed — but its what happens when the project is over that worries me. It’s amazing how  everybody abandons ship the day after launch. Chris is right,  Keep them distinct, otherwise you could be heading for trouble.

Learning from luddites: engaging with the intranet sceptics

“I’m no good with technology…”

At some stage every intranet manager has to deal with what we might term as the grumpy luddites. These are the sceptics who see no reason why they or anybody else should need to use the new intranet, social network, collaboration platform, application, whatever because

  • a) they can ask a colleague
  • b) they can pick up a phone
  • c) they can use email
  • d) they can use a spreadsheet
  • e) the old intranet was much better
  • f) I’m too busy
  • g) it’s a waste of money
  • h) why should I? etc. etc.

They tend to be naturally contrarian about technology and change, and are usually quite grumpy about it, or what we might call “comedy grumpy” but with a slight edge. These are the guys who read every cliché coming out of yet another survey about millenials, and then model their image on the exact opposite.

A grumpy luddite, digital dinosaur, techno-laggard, or whatever you choose to call them can be a threat when they are influential, well-respected or in a management position. Most likely they are a barrier to adoption in a team, unit or even division.  They may be a dissenting voice in a presentation who asks ‘how much exactly did the company spend on the intranet launch day promotional cookies when my colleagues are possibly facing redundancy”?

In extreme cases they can help to organise or be a vocal point for other dissenters, particularly if there is a mandatory change to a process involving the new intranet. (“Employee self-service…the outrage!”)  If you’re really unlucky they’re one of the stakeholders.  But perhaps most frequently they are an annoyance – a thorn in your side. You already work your socks off, and they’re being critical of what you slug your guts out to do every day. Grrrr!

Ignore or engage?

OK, at first glance this sounds fairly black and white. Just ignore these people, don’t worry about it, it comes with the territory. There are not enough hours in the day to engage with these people as a priority, and it is simply not worth the drain on time, resources and energy. I’ll go and organise an easy meeting with some early adopters instead!

Personally I think there’s a lot of sense in ignoring the grumpy luddites, particularly if you are in full launch mode, and are chasing some early success stories.  It’s also worth not responding to that critical email if you are in a precarious place time and effort-wise and are dissatisfied with your job. If a setback is going to spark resentment in you, then (as the great Scott Walker once sang) make it easy on yourself. Ignore.

However ignoring is not necessarily the most satisfying or tactical path. You could pass them on to your boss to respond, and in some cases if the intranet-sceptic is at a particular senior level, you may need to do this. But if you instead choose to engage with them, and hear their concerns you may find there are some associated benefits:

  • Everyone will respect you more for it, including the grumpy sceptic and your boss
  • You may have prevented some further dissent
  • You may learn a lot about your user population
  • You may even gain a powerful new advocate or even change agent

The value of engaging

If you have the time there are obvious benefits from engaging with the sceptics. Sometimes these people are simply trying to provoke a reaction. It may be a contrarian streak or something more personal against your department , or against somebody at a high level who has functional responsibility for your area.

If you go and see these people, armed with some good arguments, stories and metrics, and have your most reasonable / unflappable hat on then the outcome is likely to be positive. Even if they are unconvinced you may have achieved an “agree to disagree” uneasy truce, the threat from the dissenting voice will be deflected, at least for now. Perhaps you gave them a concession so they felt like they had scored something, for example that you’ll cancel the promotional launch-day cookies for when Phase 2 goes operational.  You will have earned their respect. Your boss will be pleased, you’ll be pleased.

Learning from the laggards

However the most value will come from listening to their concerns. So far this post has portrayed the sceptics as clearly wrong, but in real life it is hardly ever like that. In fact what happens if they are right? And even if you disagree with their views, do others users feel like they do? If so, then their concerns are legitimate.

A vocal sceptic tends to big-up the type of concerns which linger in the backs of the minds of other users and may already be a significant barrier to adoption. Perhaps you didn’t realise it or it wasn’t reflected in the personas you created for this project. If you spend all your time with early adopters and enthusiasts you’re unlikely to crack the tough nut of widespread adoption.

So a session with a critic might throw up some valuable questions such as:

  • Are we promoting the new intranet in the right way which deals with concerns?
  • Are we using the right vocabulary to avoid misunderstandings?
  • Is more specific training needed?
  • Do we need to do some targeted change management or communication?

It may even throw up some more uncomfortable or searching questions such as:

  • Is it really worth doing this process on the new intranet as the old way was actually better?
  • Have we actually got the design wrong?
  • Do I really understand the users as much as I like to think I do?

The last three points are potentially tricky or uncomfortable because they may point to a more significant issue which is more about the potential conflict between you as the promoter and advocate of all things intranet, and you as the guardian of all things intranet. Are you promoting something which deep down is really not very good? Have you become slightly detached from reality?

If this is the case you may need to undertake a minimum valuable repair strategy which is more honest about the intranet capability, although this may be impossible if you’re promoting something new.

Turning sceptics into advocates

If you are able to turn a sceptic and it proves that much of their concern was based on misunderstanding, then you may have gained a powerful advocate. The experience of ‘conversion’ is a powerful one and sticks in the mind. They may now even be a change agent, an enthusiastic supporter.

If your intranet sceptic is a stakeholder then this is what you really have to aim for, and it may take several battles to win the war. Dealing with a grumpy luddite who is also a stakeholder is a tricky one, and if you’re unfortunate to be in that situation and it means everything you do is an effort then you may have to take the battle to a higher level. Ask another stakeholder to intervene on your behalf and hope for the best.

If the luddism is fuelled by office politics or a poor relationship between individuals at a higher level then to be honest there may not be much you can do apart from get on with things and think about your own position.

Walking with dinosaurs

If you have the time try and engage with the luddites and the sceptics. In the long term it will give you a better perspective on users and that means you will do a better job. Acquire a thick skin if you need to and always question whether the sceptics are actually right. This can drive your intranet platform forward, achieve a better design, help you to continuously improve, and then the sceptics might be silenced.

 Steve Bynghall, January 2014

Chris says:

“Laggards are way over there on the other side of the bell curve of adoption. It’s pretty unlikely that you are going to turn them in my opinion, some people just like to whinge. But they also are likely to say the stuff that your early- and late-majority adopters are just going to think. So consider the luddites as amplifiers to a weak signal. Stay connected to reality, your colleagues aren’t robots who are going to adopt something new just because you think it is cool. Detach your hopes and dreams for your intranet from fantasy with proper user and stakeholder research and regular user testing. You may have got it wrong. Be professional and honest enough to admit to yourself.”

Make sure your intranet strategy is still going when everyone else has stopped

Everything is on hold at the moment…

Intranets and the accompany strategy which steers their direction have an uncanny knack of grinding to a halt. Sometimes this is down to their perilous state as a result from under-investment. If this is the case, we recommend special emergency measures be put in place to implement a “Minimum Viable Repair” and get it (and you) moving again.

However, intranet strategy also regularly “stops” in other organisations, including (in our experience) some of the most well-resourced and well-known global companies. Ask what the intranet strategy is and the answer is sometimes “we’re planning to update that” or “it’s on hold at the moment” or there is some sheepish mumbling while the intranet team gaze at their shoes.

Er, where’s the strategy?

In many cases the closest thing to an intranet strategy that exists is a document which was produced during the project for the last iteration or update, and which envisaged a shiny new post-launch world of continuous improvement. If you are really unlucky this is in the form of a slide deck. Sometimes there might be something more “current” which exists a woolly paragraph or passing reference to the intranet in the latest internal comms, IT or digital strategy.

There are several reasons why intranet strategy pauses including a new platform on the horizon or an organisational change, and I’ll be exploring these in more detail below. Despite these often highly plausible reasons for a stop in intranet strategy, intranets don’t stop, and the organisations which they mirror don’t stop either. Your customers and your competitors also won’t be stopping!

Intranets are a 24/7 environment which is critical to the way employees operate. Arguably they contribute to the bottom line and provide competitive advantage. They are a channel to help senior management deliver organisational strategy. So, in our view, intranet strategy and the accompany roadmap are very important, and should not be an area of neglect. Halting them misses a trick, and is the basis for under-delivering to users and stakeholders. It is basically saying it is OK to put your intranet on hold, and that is another way of undervaluing your intranet,

Having an up to date strategy and roadmap:

  • Gives the intranet team direction and a basis to plan and prioritise your activity

  • Means you are more likely to be aligned to organisational strategy and needs

  • Is the basis for continuous improvement, even if the changes are small and incremental

  • Sends out the right messages to stakeholders and users

  • Is really important in engaging site manager / super-user / publishing communities

  • You never know when you’re going to need one at the ready at short-notice

  • Leads to more job satisfaction when you deliver the goods against it

Reasons why intranet strategy pauses

There are several reasons why strategy stops. Usually it’s a combination of one or more of these: Sometimes these are good reasons, sometimes these are excuses for not having a strategy. Ultimately, you decide which.

Busy busy busy

Firstly intranet teams are busy. Very busy. They are swamped by the overwhelming operational inbox that often comes with the territory. Good intentions inevitably get trampled on by workload.

But trust on this one, getting the strategy and roadmap right is worth prioritising especially if there is a link between the direction you need to go in and the reason you are impossibly busy.

The stakeholders are seemingly unengaged

OK, ideally an intranet strategy should be reviewed, critiqued and signed-off by stakeholders who have a whiff of seniority about them, and quite possibly represent IT, Comms and HR. We know in many places that is not going to happen because the stakeholders don’t care, or more likely are too busy to give it proper attention.

If this is the case and there isn’t much you can do about it, assume that the stakeholders trust you. They know the intranet is in good hands. Assume that if the intranet was failing they absolutely would take an interest. If they trust you with the intranet, they also trust you with intranet strategy. It’s up to you to define this. Even if the output gets waved under their nose, and they nod, take that as approval. Seeing something coherent and well-argued, may actually surprise them, and could lead to a budgeting decision. Someone has to do intranet strategy, and it looks like it is you.

There’s a new Director of Comms / IT / KM / HR on the way

So there’s a new owner of the intranet on the way.  The intranet strategy was going to go through its annual review but we might as well wait for the new Director to come in to wait for their input.

Personally I think waiting is a mistake. It can take ages for a new senior stakeholder to get to know the business, and for the intranet to be properly on their radar. Let’s say it could take six months. Given that senior replacement appointments might be known about six months in advance, then it could be up to 12 months before intranet strategy comes up as a topic for discussion.

Having an up to date intranet strategy already in place sends out all the right messages to someone who is probably your new boss. It also ensures continuity and means that you are more likely to have your dabs all over the strategy.

In larger organisations there may be a steering committee which ratifies the strategy and they might want to halt any updates to it based on the new owner, but if you can influence them, carry on as business-as-usual.

There’s a new new intranet platform or SharePoint on the horizon

The biggest mistake intranet teams make is putting everything on hold while IT makes up its mind about a new platform. We may be going to SharePoint? How long before a) IT make up their mind b) The agreements are signed c) The project is implemented d) The legacy systems are phased out. We’re talking potentially years! So until you’ve seen that bit of paper signed, assume it isn’t happening and everything is business-as-usual.

Moreover strategy should be largely agnostic of technology. And although inevitably your direction probably does need to reference an impending decision by IT e.g. perhaps heavy customisation isn’t such a good idea, many of the improvements you influence are around information architecture, findability and content management.

Many improvements you make in these areas are excellent preparation for a platform change. For example having an engaged publisher community who are clued-up and care about what they are doing is not only going to help you every day, but will come into its own when you go for content migration in any project,

We need a new platform, nothing else matters

If the old intranet is creaking and clearly needs replacing, a new iteration might be uppermost in your mind, but perhaps not for anybody else. Banking on a new intranet is definitely putting all your eggs in one basket. There are always things to move forward on your existing platform. A new IA, a new design, a bit of well-positioned workflow…but you may need to veer into Minimum Viable Repair territory here. Whatever you do, don’t fall into the trap of assuming a new intranet is all-or-nothing, because it may well end up as nothing.

There is a company merger or reorganisation

Inevitably this is going to hijack your intranet strategy and operations so they are going to more short-term, but it can also influence it for the better by assimilating ideas from the new business, or give an opportunity to introduce things you have been thinking for a while.

The point is a merger can force a rethink of strategy but it doesn’t necessarily mean it is completely divorced from existing strategy, and you can’t move forward with a particular direction. You can also learn to plan for future change, particularly if your company tends to acquire other businesses.

Strategy doesn’t stop

Do any of these scenarios sound familiar?  Perhaps something else in your organisation halted your intranet strategy?  I think the main issue here is that teams need to prioritise strategy. It is what informs your operations and keeps the intranet relevant. Don’t fall into the trap of having an intranet with no direction, because you’re waiting on something else to happen or a decision to be made. 

Steve Bynghall, January 2014

Chris says:

“A strategy is a plan, people. How can you not have a plan? But, as Steve says, we see it all the time. Intranet teams mumble something about the intranet strategy being developed but they just need something to go their way. You know, I wish more of them would look us in the eye with some steel and just say ‘no’. Grab whoever is interested and document your plan for the next 3 to 18 months with what you know now. Imagine it is code and put some if{} else{} statements in. If we get the go-ahead for SharePoint or the new ESN we’ll do this, otherwise this is the plan and we will concentrate some efforts here – let it emerge. But whatever you do, know what you are doing, write it down and share with everyone who cares. And one last thing: if you don’t have the capability to deliver anything of value strategically, revel in being tactical. That’s your strategy right there, so write it down and take it to your bosses. They’ll blush.”

Intranet Directions elsewhere January 2014

So here are a few other things we’ve been up to on and off the digital slopes:

Chris elsewhere

A new year. Again. The older you get the quicker it rattles past. I’ve got a list for self-improvement that stretches beyond the bounds of the reasonable, particularly learning R and bolstering/remembering my stats chops.

Over in DWG world I’ve been busy with a spot of interesting benchmarking assignments as well as polishing off a couple of research papers (members only I’m afraid) one on the current state of employee directories, and one on “Measuring Communications”. I’ve also done a load more in a series of digital workplace posts for DWG, which seem to have been very positively received :

Other than that it was Christmas break and spending time with the family as we watched the salty Brighton rain slosh against the windows, and with the South Coast greyer than an actuary’s suit I didn’t get to shoot a frame that didn’t include a hat from a Christmas Cracker.

Steve elsewhere

For the  past six weeks or so I’ve been working on various different projects. I’ve got a lot of work-in-progress.. Little bits here and there.  Intranets. Writing. I’ve even co-presented IBF Live. Oh, and there was all that Christmas and New Year stuff.  I am also fantastically hungry because I am trying to lose weight, as well as doing that seven minute work-out thing every day which featured in the New York Times.

The writing I have done on my personal Two Hives blog  and elsewhere is also a little bit random, but includes a focus on a South Korean steel company who are doing very interesting things with their digital workplace, some fence-sitting intranet predictions for 2014 plus a look at the freelancing crowdsourcing markets, which is basically nothing to do with intranets. Here are the links: