Web Publishing Model Project: evaluating and presenting our data

We’re almost 2 months through the project and have made some very interesting discoveries after our focus groups, web surveys and conversations with other Universities. The level of contribution has been incredible and it has been invaluable in preparing for our next phase of work which is to filter through the solutions and applying their pros and cons to the requirements. We plan on doing this by holding 3 separate “solution group” meetings with team managers, consultants, web developers and web designers from both the Web Solutions team and the Web Development team.

Before this though, what we immediately noticed is that we have a huge amount of requirements and documentation that needs to be structured in a way that doesn’t feel overwhelming and that allows us and our stakeholders the ability to have what is the equivalent to an executive summary. That’s where trump cards come in.

Trump cards

Constructing our data into a funnel would allow the greatest level of control and understanding of all of our documents and spreadsheets.

Trump card > Evaluated analysis > Raw data

We’ve created trump cards for the Universities website requirements and also for every potential solution that we have investigated thus far giving us our initial, easily digestible entry point into the wealth of information we have gathered. The idea is that is will allow us to have a constructive conversation by evaluating each section and hopefully get a high level views of what may be suitable or not suitable in the first review round.

Requirements card

  • Core requirements: everything that should come as standard and our minimum requirements for any solution
  • Other requirements: this are functions that we are aware our users and publishers want from our investigation which some solutions may provide
  • Survey: based on responses from our web publishers. It’s our constant reminder of what you guys like and dislike about the current solution so that we stay on track.
  • Case studies: same as above but with the personal element added. We are doing this for you and ensuring that we take your quotes on board and remember to remind ourselves of our discussions we can ensure you get a solution that is suitable

Solutions card

  • Very similar to the requirements card but offers a more “tick box” like interface.
  • Will be used during our solutions group meetings but also to add to this blog to give our users and stakeholders an update on the progress we are making
  • Allows enough flexibility to write notes, and answer questions, but enough structure to ensure we make use of our time efficiently.

Evaluated analysis and core data

Every trump card also leads to a whole set of documents stored on a shared drive which is accessible by the two teams. This is the natural progression from the trump cards as it provides substantially more detail of all the requirements, meeting notes, focus group notes and technical analysis of the potential solutions. It will aid discussion and prevent unnecessary research with a large group of staff so that we can be as effecient as possible.

What’s next…

This project is begin to heat up and some very interesting discussions will be happening internally within IS over the next 4 weeks but we’ll ensure we’ll keep you up to date on what is happening and where we are going. For those interested, we will be entering our first meeting with 10 potential solutions (7 of the shelf and commercial, 3 bespoke) and the plan is to bring those down to a number where we can begin some more in depth investigation in preparation for the¬†second solutions meeting.

One response to “Web Publishing Model Project: evaluating and presenting our data

Leave a Reply