Product Management at MojoTech

Building the right thing is the most important thing.

Building it right is a close second

Product Managers (PM) occupy a unique position at MojoTech. They are responsible for product quality, project status and client satisfaction.

Your product is their ultimate responsibility and they are the central point of contact for all stakeholders involved in the project:

  • Clients depend on their PM to help them define and refine their vision and look to them to provide constant visibility into project process and progress.

  • Designers work hand-in-hand with the PM to understand the product’s users, pain points, and goals. They synthesize user feedback, analytics, and our client’s vision to define features and experiences that address the highest priority opportunities.

  • Engineers have feature-specific questions and look to the PM to have clearly defined user stories.

  • Mojo Account Managers look to the PM for staffing recommendations and budget tracking as well as early warnings of potential project risk or client-side blockers.

product management venn diagram

Starting Strong

At the start of every project, we immerse ourselves in our client’s business; absorbing the fundamental factors behind the product vision in our Product Discovery Process. This gets everyone up to speed on the people, process and technology that will be used to bring the product to life. There are four steps:

  • Analysis
    Visioning, users/roles, challenges, goals, success markers

  • Validation
    User interviews, risk assessment, prototyping, constraints

  • Consensus
    User flows, road mapping, tech stack, design principles

  • Planning
    Sprint Zero, feature epics, milestones, resourcing

Being Agile

We follow an Agile/SCRUM format — building and deploying working software in one or two-week increments (sprints). This pace requires timely input from clients and MojoTech alike to ensure we achieve the desired velocity consistently.

backlog illustration


sprint planning illustration

Sprint Planning

estimation illustration


development illustration


daily standup illustration

Daily Standup

testing illustration

Testing & QA

deployment illustration


sprint retrospective illustration


A critical part of regular sprint planning is prioritizing new feature requests. We ask questions, challenge assumptions and encourage prioritization based on factors such as value to the business, user needs, cost of implementation and timeline/resource constraints.

We go through this prioritization exercise a LOT because building a great product is an ongoing, dynamic experience and we’re not afraid of changing requirements or new ideas.

We know that with a great framework for prioritization, we’ll ultimately build a successful product, in the most efficient way.

The more software you build without releasing it, the greater the likelihood you are building the wrong thing.

Radically Transparent

Software is a manifestation of human input, and its current state of evolution can be a tricky thing to pin down. Our Product Managers have an array of tools at their disposal to ensure complete visibility into your project over time, and at any given point in time. Here are a few of our favorites:

g-suite logo
pivotal tracker logo
basecamp logo
dropbox logo
GitHub logo
invision logo
slack logo
trello logo

MojoTech’s sharpest tool set, however, is not manifested in a piece of workflow software. The hallmark of every successful project at MojoTech is collaboration. Building great software is hard and requires engaged, informed players on both teams. A project is complete when it starts working for you, rather than you working for it.

A photo of Lauren Mullaney-Reid

Helping to manage expectations and perceptions is important, but providing insights into how decisions imbue the product with maximum value is truly where the PM can be a helpful partner with a client.

Lauren Mullaney-Reid,Product Manager