At Step Two Designs we're frequently involved in intranet projects with Microsoft SharePoint. In fact for me personally, every single project I've worked on in the last 12 months has been involving this behemoth platform. In every project, we're presented with both classic intranet scenarios and increasingly common requirements and challenges directly related to SharePoint. I've written about a few of them before. Our role in these projects is increasingly defined, as James describes in a post published today:
In a SharePoint project, we don’t deploy or write code (there are plenty of people who do). Our role is to work with or alongside the geeks, providing the 10-15% of planning and design activities that ensures project success.
We draw on our unique experience, insight into intranet projects across hundreds of organisations, and a clear understanding of the SharePoint platform. Bringing this together, we provide the techniques, answers, examples and screenshots that maximise the value of SharePoint investments.
We can also provide ongoing support, to keep things on track, and to see the project through to a successful conclusion.
This role has proved immensely valuable to the projects we're involved with. Too often, it's easy to get drawn into the extreme technical nature of SharePoint, and lose sight of the intranet's space and place within, particularly if the project or implentation is being strongly driven by IT.
Read James' full post for more on this, and other recent SharePoint intranet posts that reflect some of the more recurring discussions we're having on the topic.


Recent Comments