Skip to content
Tobistech

Inside Tobistech

How a Small Team Decides What Not to Build

2 min read

At Tobistech, our small team employs a structured approach to decide what not to build in the realm of shipping software. By focusing on clear criteria and strategic alignment, we ensure that our resources are directed towards the most valuable projects.

Understanding Core Objectives

Before evaluating potential features or products, we clearly define our core objectives. These objectives align with our overall mission and vision, guiding our decision-making process. By having a strong foundation, we can better assess whether a new project aligns with our goals.

Criteria for Exclusion

We apply specific criteria to determine whether to exclude a project or feature. Some of the key factors include:

  • Misalignment with strategic goals
  • Limited market demand or user interest
  • High resource investment relative to expected return
  • Redundancy with existing products or features
  • Technical feasibility concerns

Prioritising User Feedback

User feedback plays a crucial role in our decision-making process. We actively listen to our users and analyse feedback to identify what truly matters to them. If a proposed feature does not resonate with our users or solve a significant problem, it is likely to be put on hold or excluded.

Balancing Innovation with Feasibility

While innovation is important, we must also consider feasibility. Our team evaluates the technical and operational capabilities required to build a feature. If a project is too ambitious or unrealistic given our current resources, it may be set aside. This helps us maintain a sustainable development pace.

Collaborative Decision-Making

Collaboration is key in our small team. We hold regular discussions to ensure that all perspectives are considered when deciding what not to build. By involving the whole team, we leverage diverse insights and experiences, leading to more informed and balanced decisions.

Learning from Past Decisions

We review past projects and decisions to refine our approach continually. By analysing what worked and what did not, we can improve our criteria and processes for future exclusions. This iterative learning process helps us adapt and stay aligned with our core objectives.

Conclusion: The Importance of Saying No

Deciding what not to build is as crucial as determining what to pursue. At Tobistech, our small team's disciplined approach ensures that we maintain focus on projects that truly align with our mission and deliver value to our users. By adhering to our criteria, prioritising user feedback, and fostering collaboration, we can navigate the complexities of product development effectively.

Tobistech

Built by the team behind four apps.

Tobistech builds and operates apps across health, sports, trading and faith, and partners with businesses to build exceptional software.