Session Slides by Rob Rose


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The Development Process What should the phases of a Web project look like? What are the deliverables? How long should they take? Most Important: How involved do you need to be? Managing Your Site Proper care and feeding of your new site Is everybody involved? Budget General budgets we're seeing for these processes Q/A Resources
  • How do I get started… Start by “looking in”. What do you need? Not want, BUT REALLY need? Assemble requirements from stakeholders. Broad business strokes – not a 500 page document Out of this document comes an RFP This assumes you’re going to outsource Not terribly different if you’re not – just different audience – you should still get people committed to a timeframe and “budget”. RFP Selection Process Limit yourself to a short list of firms. Remember, a 50 page proposal from 5 firms is 250 pages of bed time reading. Request “solutions” not a feature/function matrix… You’ll have your own criteria – select a firm that’s fits your needs….
  • Then, get ready to do it all again…. Discovery You’ve missed something – guaranteed. You and your firm (or internal team) need to be on the same page about what’s going to get built. Again, not a 500 page document – but an agreed framework of solutions, and tactics. The deliverable: The Statement of Work Details the BREADTH of the scope. Top Level needs and priorities Parking Lot set up for phase 2 wishes, wants and needs Only the beginning of paperwork. No Pretty Pictures yet.
  • The Functional Specifications comes out of Discovery Takes the breadth of the Scope and details the DEPTH Defines the “what” is going to be built Identifies the audience for your site Identifies the browsers and platforms Identifies each piece of functionality and how they will work Includes Wire Frames, results of Content Inventory Helps to define the requirements for any software applications that will be purchased or subscribed to
  • Probably the most important step in web site design Can make or break your site 6 months down the road Don’t skip this step! Firm should deliver Wire frames that detail out the function. Wireframes are not a site map – and they’re not hand-drawn. Walk through the wire frames with your partner Sign off on the wire frames – your designer will love you
  • Now come the pretty pictures Based on wire frames, design should go very quickly With little or no surprises (at least bad ones) Resist the urge to pick elements from each design… There’s usually a good reason… By far the most emotional and difficult phase The people who said “I don’t care about this” suddenly do Keep the cooks in the kitchen to a small group
  • The longest phase of the project – and least interesting (for you) What do you during this phase? Nothing….just kidding. But really, you sit back and watch the magic. Your role is to be available for reviews, questions and a little QA Software selection can also be part of this phase…
  • Func Spec sign off – Development begins Integration 2-4 weeks HTML Pages Content Migration 4-6 weeks Move current site to new system (more on this later) Custom Development 4-6 weeks Build any tools, hooks, custom apps that new software cannot handle QA 4-6 weeks – CANNOT STRESS HOW IMPORTANT THIS IS Stabilization 2 months There WILL be bugs – this is software
  • What is your development partner delivering as the final deliverable. You could wind up with a nicely designed set of templates and nothing to do with them. If you didn’t consider how you’re managing your new web site at the beginning – make sure you do. The solutions that are driving the functions of your web site management are just as important as the design aspect. CMS Solutions, CRM Solutions, Web Site Analytics, Web Site Hosting – and yes Custom Application Development…. But this last piece you’ve got to be careful about. The key is to not underestimate the management of the management and support of your new baby. Know what you are signing up for – and more importantly, make sure everyone knows what they are signing up for. This is particularly true for Web 2.0 – How many times do you hear – I need Web 2.0 features. You’ve got to be able to support those features ongoing. One rant is not a blog. One audio file is not a podcast. Community isn’t community with a hundred “me too’s” on a bulletin board. Developing a support and management strategy is arguably MORE important than developing a design strategy – because guess how long design took – and guess how long it’s going to be till you re-design again. It will be a lot shorter if you don’t have a good strategy.
  • 10 Buying a CMS is still very hard. It’s still confusing – and all the vendors out there aren’t making it much easier. Most software vendors aren’t very interested in you becoming successful – what if there were vendors who cared… 8. Most web site management apps STILL go unsupported after launch. What is your IT Guy signing up for when you walk into the room and ask. 7. Open Source solves the wrong problem. Buying the software is the least expensive part of getting the software. 6. Most software is overwrought with features that are rarely used – and the support isn’t there to help customers get the most out of the features they need.
  • Buying a CMS to have a better web site is like buying a mop to keep the kitchen clean – it’s not going to work until you actually manage and support it and use it. 4. Implementation of software is easy – it’s the support and management that’s hard. 3. Most organizations have few, infrequent users of software – how easy is it to use and how easy is it to find training for those infrequent users. 2. Companies buy software either because some consultant or the vendor convinced them it would provide ROI – but nobody ever measures it. 1. Conten Migration sucks.
  • Shhh… Here’s a secret. Content Migration is hard. It’s very easy to get turned around… No matter what any vendor tells you – No, it’s not as easy as pointing a “system” at the old site. No, it’s not as easy as *Just* importing the content into the new system No – there’s no “just” in there at all… Develop a plan – and follow it. Even if you think you know all your content you don’t – so develop a content inventory and you can start on it right away. Repositioning? Rewriting? Find out how much and where it will go in the new site heirarchy. Don’t underestimate the time it will take. Assuming you have a reasonably sophisticated set of content – figure it will take between 3 to 5 minutes to migrate a page by hand into your new site. Yes, that means a 5000 page site will require 416 hours – or approximately 50 business days to be complete.
  • Arguably the MOST important step in your whole project Rolling out to users who will take ownership of aspects of the site is very very important Don’t give your project a bad rap – just when it’s about to succeed: 5 Things to keep in mind: Usability for all the applications for managing. Make sure that whatever solutions you pick, the interfaces are easy to use. Sometimes less features is better. Sufficient training and support. Have a plan for training and support on ALL of the applications – and how they work together. Organizational communication. Who’s responsible for what. Make sure that ongoing – everybody from IT to Marketing to Communications knows wh’s responsible for the apps Review and Iterate – The Web Site is a process – not a product make sure that ALL through your development process and your Rollout that phase two items are noted and then iterated. Start small, and grow.
  • When you’re ready to iterate the web site, start again… If you’re measuring and iterating, you know what’s working and what’s not. If you are launching in bite sized chunks you haven’t “over featured” your web site. If you’re supporting it well – you know who’s responsible for what and where any needs for additional tools or features are to make it more efficient. Your partner should now know the system and will be your trusted advisor. Your solutions can be plugged in and out based on the value they are creating. Your web site will be affecting the overall success of your organization.
  • Session Slides by Rob Rose

    1. 1. We Need A New Web Site! Doing Your Web Design Right
    2. 2. Introductions <ul><li>Michael Weiss – CEO Imagistic </li></ul><ul><ul><li>Internet Software and Services Company </li></ul></ul><ul><ul><li>10 Years experience developing Web sites for Non-Profits </li></ul></ul><ul><li>Robert Rose – VP Product Strategy CrownPeak </li></ul><ul><ul><li>10 Years working with organizations of all sizes – web infrastructure design and strategy </li></ul></ul><ul><ul><li>Specialization in Internet marketing and communications </li></ul></ul>
    3. 3. Plan for your next site Re-design <ul><li>The Development Process </li></ul><ul><li>Managing Your Site </li></ul><ul><li>Budget </li></ul><ul><li>Q/A </li></ul><ul><li>Resources </li></ul>
    4. 4. The Development Process: RFP <ul><li>How do I get started… </li></ul><ul><ul><li>Start by “looking in”. </li></ul></ul><ul><ul><li>What do you really need? </li></ul></ul><ul><ul><li>Talk to your people! </li></ul></ul><ul><ul><li>Out of this document comes an RFP </li></ul></ul><ul><li>RFP Selection Process </li></ul><ul><ul><li>Get a short list of firms </li></ul></ul><ul><ul><li>Request “solutions” </li></ul></ul><ul><ul><li>You’ll have your own criteria – select a firm that’s fits your needs…. </li></ul></ul>
    5. 5. The Development Process: Discovery <ul><li>Discovery </li></ul><ul><ul><li>Do it all again…. </li></ul></ul><ul><ul><li>You’ve missed something. </li></ul></ul><ul><ul><li>Not a 500 page document </li></ul></ul><ul><li>The deliverable: The Statement of Work </li></ul><ul><ul><li>Details the BREADTH of the scope. </li></ul></ul><ul><ul><li>Top Level needs and priorities </li></ul></ul><ul><ul><li>Parking Lot </li></ul></ul><ul><ul><li>Paperwork. </li></ul></ul><ul><ul><li>No Pretty Pictures yet. </li></ul></ul>
    6. 6. Development Process: Functional Spec. <ul><ul><li>Details the DEPTH </li></ul></ul><ul><ul><li>Defines the “what” is going to be built </li></ul></ul><ul><ul><li>Identifies the audience </li></ul></ul><ul><ul><li>Identifies each piece of functionality </li></ul></ul><ul><ul><li>Wire Frames, Content Inventory </li></ul></ul>
    7. 7. The Development Process: IA <ul><li>THE most important step in web site design </li></ul><ul><li>Don’t skip this step! </li></ul><ul><li>Wireframes are not a site map </li></ul><ul><li>Wireframes are not hand-drawn. </li></ul><ul><li>Sign off on the wire frames – your designer will love you </li></ul>
    8. 8. The Development Process: Design <ul><li>Now come the pretty pictures </li></ul><ul><li>By far the most emotional and difficult phase </li></ul><ul><li>The people who said “I don’t care about this” suddenly do </li></ul><ul><li>Keep the cooks in the kitchen to a small group </li></ul>
    9. 9. The Development Process: Development <ul><li>The longest phase of the project </li></ul><ul><li>What do you during this phase? </li></ul><ul><li>Your role is to be available for reviews, questions and a little QA </li></ul>
    10. 10. The Development Process: Typical Timeline <ul><ul><li>Integration </li></ul></ul><ul><ul><ul><li>2-4 weeks </li></ul></ul></ul><ul><ul><li>Content Migration </li></ul></ul><ul><ul><ul><li>4-6 weeks </li></ul></ul></ul><ul><ul><li>Custom Development </li></ul></ul><ul><ul><ul><li>4-6 weeks </li></ul></ul></ul><ul><ul><li>QA </li></ul></ul><ul><ul><ul><li>4-6 </li></ul></ul></ul><ul><ul><li>Stabilization </li></ul></ul><ul><ul><ul><li>2 months </li></ul></ul></ul><ul><ul><ul><li>There WILL be bugs – this is software </li></ul></ul></ul>
    11. 11. Now We’re Ready To Manage It!! Er…. I think we are….
    12. 12. Managing Your WebSite: What Now? <ul><li>What Did You Get? </li></ul><ul><li>What Have You Signed Up For? </li></ul><ul><li>One Rant Is Not A Blog </li></ul><ul><li>Guess How Long Till You Get To Do It Again? </li></ul>You Redesigned And All You Got Was The T-Shirt
    13. 13. Managing Your WebSite: Tools? 10. Buying a CMS is still harder than buying your first house! 09. Most CMS vendors don’t help customers be good web site managers 08. Most CRM, CMS, Hosting and Web Analytics implementations still go unsupported after launch 07. Open Source solves the wrong problem 06. Customers overpay for features they’ll never use, and are rarely delivered the services they need. Top 10 Software Dirty Little Secrets….
    14. 14. Managing Your WebSite: Tools? 5. Buying a CMS to have a better web site is like buying a mop to keep the kitchen clean 4. Implementation is easy. Management is hard. 3. Most organization have few, infrequent site management software users 2. Companies buy software based on ROI, but don’t ever measure it 01. Content migration sucks Top 10 Software Dirty Little Secrets….
    15. 15. <ul><li>Some Vendors won’t volunteer the truth…. </li></ul><ul><li>“ Plans are worthless. Planning is priceless” - Winston Churchill </li></ul><ul><li>5 5000 416 50 </li></ul>Shhhhh…..Content Migration Is Hard! Managing Your WebSite: Migration?
    16. 16. <ul><li>Usability </li></ul><ul><li>Training </li></ul><ul><li>Communication </li></ul><ul><li>Review. Measure. Iterate. </li></ul>Managing Your WebSite: Launch & Rollout
    17. 17. <ul><li>Measure twice… confuse.. err.. Impress your boss </li></ul><ul><li>Learn from Google </li></ul><ul><li>Support it – and it will work. </li></ul><ul><li>Business decisions, not triage </li></ul><ul><li>Best-of-breed NOT all-in-one </li></ul>Managing Your WebSite: Back To Strategy
    18. 18. <ul><li>Sample Development Budgets </li></ul><ul><ul><li>Small: $10,000 to $50,000 </li></ul></ul><ul><ul><li>Large: $50,000 to $100,000 </li></ul></ul><ul><ul><li>Time is money. These projects take time. </li></ul></ul><ul><ul><li>Negotiate rates but hours are hours. Compare apples to apples </li></ul></ul><ul><ul><li>$20 an hour to $200 an hour. </li></ul></ul>Budgets This isn’t Poker. It’s a Partnership
    19. 19. <ul><li>Web Site Management Applications </li></ul><ul><ul><li>Open Source isn’t free. </li></ul></ul><ul><ul><li>Site Mgmt Application/Support: </li></ul></ul><ul><ul><li>CMS or CRM: $20K-$100K annually </li></ul></ul><ul><ul><li>Analytics – Free to $500+ annually </li></ul></ul><ul><ul><li>Hosting - $50/mo to $1,500/mo </li></ul></ul>Budgets This isn’t Poker. It’s a Partnership
    20. 20. <ul><li>10. Never think this going to take 4 weeks </li></ul><ul><li>9. Never think you can do this alone </li></ul><ul><li>8. Never skip the IA Phase </li></ul><ul><li>7. Never do this without an RFP </li></ul><ul><li>6. Never send the RFP to more than 5 firms </li></ul><ul><li>5. Never choose a vendor based on price alone </li></ul><ul><li>4. Never ask your IT Manager to manage this process this alone </li></ul><ul><li>3. Never start without a budget in mind </li></ul><ul><li>2. Never start this process without key stakeholders involved </li></ul><ul><li>1. Never hire your boss’ nephew </li></ul>Mike & Robert’s Top 10 Never Do This….
    21. 21. <ul><li>Rob Rose </li></ul><ul><li>[email_address] </li></ul><ul><li>Mike Weiss </li></ul><ul><li>[email_address] </li></ul>You Have Questions… come on you know you do.