AV Business Hackers
Approach

We transfer any challenge to a digital product
through 6 phases in 12 weeks.

Purpose

Understand the vision, and uncover market-user insights

Time

1 - 2 weeks

Activities

  • Define what success looks like by listening and learning about your business to understand your hopes, fears, and vision for this project, and develop clarity on your "Why".
  • Conduct lean market research to understand the current marketspace and winning business models, and what makes them winning.
  • Conduct lean user research to understand who are current the customers in this market, and develop a behavioral understanding of why they buy or don't buy.
.

Outputs

  • Identify the project team to identify who is responsible for each part of the project task.
  • Draft vision and principles that will define what success looks like and how we will know if we have achieved it
  • Develop lean market profile that identifies the nature of the competition in the current marketspace and winning business models, and why they are winning.

Purpose

Deploy a disruptive strategy

Time

1 - 2 weeks
.

Activities

  • Align with innovation and disruption to uncover low-end and new-market entry points, using state-of-the-art technology and various business models.
  • Identify the customer “job-to-be-done” by interviewing customers and understanding what and why they “hire” certain products to achieve their goals.
  • Organize for innovation by developing the resources, processes, and loot(profit) formula required to execute the disruptive strategy.

Outputs

  • Create a new business model that has an ability to disrupt the market at scale.
  • Create a customer “job-to-be-done” list of prioritized functions, as well as personal and social experiences the product or service needs to deliver. This includes how the customer will be able to access or consume the product or service.
  • Develop a disruptive strategy that outlines the course forward and acts as a strategic pirate map.

Purpose

Key hypothesis validation, part 1

Time

1 week
.

Activities

  • Product mapping to identify all the end-user touchpoints, the challenges in each of these ports of harbor (steps), and decide on a target to focus on the design sprint.
  • Sketch competing solutions that have the highest potential of addressing the end-user wants and needs.
  • Decide on the solution to prototype.
  • Develop low-fidelity prototype to test the key hypothesis with the end-users.
  • Test prototype with end-users and validate or invalidate the key hypothesis.

Outputs

  • Wireframes and Story-map to outline the product and customer journey.
  • Decide on the right prototype to develop, if key hypothesis was validated. If successful we’ll execute on the development of the prototype.
  • Determine the next key hypothesis to test if the hypothesis was invalidated.
  • User testing the product from real customer to assess the effectiveness and potential success of the product.

Purpose

Key hypothesis validation, part 2

Time

1 - 2 weeks

Activities.

  • Conduct experience workshop to identify the experience attributes which need to be met
  • Conduct visual research to identify the color palate and typography expected to be most effective in attracting the end user.
  • Develop different UI screens based on the different experience attributes.
  • Decide on UI set to sail forward and develop.
  • Develop content strategy

Outputs

  • Organized and documented UI components which include displayed colors, typography, and UI components.
  • UI guideline documentation
  • UI stack that will be provided to programmers to develop.
  • Content strategy

Purpose

Develop actual product

Time

6  weeks
.

Activities

  • Prioritize feature set for development using the UI stack.
  • Upload UI files to developers and align on feature set and path forward.
  • Convert the UI stack into an actual product
  • Assign product manager who will completely manage the software development process. As well as ensure all stakeholders are on board and updated.

Outputs

  • Prioritized Product Pirate Map to specify which feature will be developed first and why.
  • Weekly update report on software development progress.
  • The end product!

Purpose

Unearth and nurture a growth strategy

Time

2 - 4 weeks
.

Activities

  • Conduct growth hacking strategy that matches the persona.
  • Conduct A/B testing on potential new features to minimize risk.
  • Develop an automated email marketing plan
  • Implement SEO optimization

Outputs

  • Automated email marketing dashboard
  • ROI and risk assessment scorecard of planned features.
  • Increased ranking on search engines.
  • Forward-facing content strategy