Stackup 2017-08-23T10:02:07+00:00

Project Description




Stackup ( is a web app and browser plugin that tracks, measures, and reports online reading for students. Stackup provides the accountability needed to measure progress, while giving students the freedom to read what they want. Stackup was founded in 2014 by Nick Garvin of Denver, Colorado. Since then, Stackup has grown into an invaluable resources for dozens of schools and thousands of students.

Requirements & Deliverables

As a K-12 Student, I need a way to track and display my time reading online, track improvements in my reading skills, and learn new interests outside the classroom. Further, I am seeking additional content related to the subject areas that I am most interested in.

As a K-12 Teacher, I need a way to quickly and easily create and track reading goals in the classroom. In addition, I would like to give students credit for online reading, discover their interests in more depth, and keep track of their progress, automatically.

As a School District, I need a digital resource to capture valuable data about (online) reading habits for individual students and classrooms that is simple to install district-wide.

As a Business, I need to develop a unique, engaging and fun platform to track students reading habits online. Further, I need to provide enough value for the user types to develop a profitable revenue stream.

  • Project Objectives and Approach

  • Business Requirements

  • User Research

  • Personas

  • Content Strategy

  • Site Maps and Task Flows

  • Wireframes and Annotations

  • Prototyping

  • Visual Design

  • Transition to Development

  • Front End Development


Project Objectives and Approach

Kick-off meeting

  • Identify key stakeholders and invite them to a formal kick-off meeting
  • Discover the 5W’s for the feature
  • Lead an open discussion on how to best facilitate what are thought to be the initial users needs and business goals
  • Outline how to measure success by using the Google H.E.A.R.T. framework

Project plan

  • Outline; key deliverables needed to inform design decisions, who is responsible for completing them, when they were due and how we’ll communicate (e.g. setting expectations)

Business Requirements

Stakeholder interviews

  • Interview business stakeholders to gain more insight on what their goals are and what data points need to be extracted
  • Document each interview via interview template

Competitive analysis

  • Study several direct and non-direct competitors solutions for similar features and design patterns
  • Capture screenshots of workflows
  • Design a competitive landscape matrix

User Research and Personas

Heuristic Evaluation

  • Review the existing application in-depth to understand opportunities for improvements
  • Use Nielsens list of heuristics to evaluate usability best practices
  • Define and prioritize which areas have the room for most improvement
  • Use the information to inform the business and design decisions (Keynote/Powerpoint presentation)

Define user groups

  • Create a list of attributes that will help define the different user types
  • Organize common attributes in to groups
  • Define and prioritize which groups will have the biggest impact on the business

User research

  • Setup tests, recruit participants, conduct research sessions, document feedback, and report to the business
  • Chosen methods include; user interviews, email surveys, and in-person focus groups
  • Use the information to inform the business and design decisions (Keynote/Powerpoint presentation)

Develop personas

  • Using the information learned from the business and user research, create documents that describe the typical target users for BeVisible
  • Distribute persona documents to executives and other stakeholders
  • Update personas as we learn more information through web analytics, customer services, etc.

User Story Map

  • Define the users end goals and the steps needed to be performed within the system to accomplish them
  • Work with stakeholders and subject matter experts within the organization to outline the users path through the system
  • Prioritize the features and organize the work into releases
  • Add tasks to backlog

Content Strategy

  • Inventory content that we have now (images, videos, pdf’s, text, etc.)
  • Discuss what content needs to be created/updated (marketing, social media, emails, website, app, help context, error messages, etc.), who will be doing it, and how often it needs to be updated
  • Organize/group all content and attributes in a spreadsheet (content matrix)
  • Prioritize content (hierarchy) and define where content would be best placed
  • Distribute content matrix to executives and other stakeholders

Wireframes and Annotations

  • Using the task flow diagrams and requirements, create wireframes that outline the user interface components necessary to complete the users goals
  • Work with the product engineering team on technological limitations
  • Annotate actions needed to perform the users task
  • Annotate empty states, error and success states other hidden content
  • Present the wireframes to the business for acceptance

Paper Prototyping

  • Print each view, pin on the wall and create a walkable area
  • Test the interface with key stake holders and end users, document results and make corrections

Visual Design

  • Create high-fidelity mockups that represent the exact design of the pages of the web app
  • Generate a visual style guide that outlines the common fonts, colors, logos, images and interface patterns
  • Use the visual designs as the standard for acceptance testing
  • Design and develop social media pages and responsive email templates

Transition to Development

  • Using CSS, HTML and JavaScript develop HTML Page Templates for each page of the web app
  • Test the design on multiple devices to ensure consistency and usability when responsive
  • Package and deliver the page templates to the engineering team and assist in implementation

Measure and Report

  • Monitor web and social analytics
  • Measure happiness by surveys, interviews, and contextual inquiries (user journey mapping)
  • Measure engagement by time spent on the new page for the user type within the next 30 days
  • Measure adoption by what percentage of the user type were targeting will visit this new page within the next 30 days
  • Measure retention by how often the user type re-visits the page within the next 30 days
  • Measure time on task by analyzing workflows and contextual inquiries
  • Reanalyze data every thirty days, compare it to the previous period, look for insights
  • Send monthly high-level reports (with visuals) to key stakeholders
  • Enter new items into the product backlog for future releases

Ready to Talk?


Contact Antfarm Today