Every product goes through stages where different users emerge and your development approach must adapt. The trap is using one process for all phases without regard for market signals.
Tickets Sales, Inc. (TSI) is a seed-funded startup planning to enter a stable yet competitive ticket sales market in New York City. The management believes their bulk-purchasing model and real-time distribution network will deliver better, faster service than established players like Ticket Master and TKTS. The actual job here is to use frameworks to understand how TSI’s product will evolve, who the users are at each stage, and which software development lifecycle (SDLC) approach best fits their context.
The stakes are clear: launching too early without understanding user dynamics or choosing the wrong development process can waste capital and miss market fit. Your job as a product manager is to apply the product life cycle (PLC) lens to user segmentation and pick an SDLC that balances speed, flexibility, and risk.
The product life cycle reveals who your users are — and when
The product life cycle is a fundamental framework that maps the evolution of a product through stages: introduction, growth, maturity, and decline. Each stage corresponds to distinct user groups with different needs, behaviors, and expectations.
Introduction stage: Your product is new to the market. Users are innovators and early adopters — those willing to try a novel solution despite rough edges. They tolerate bugs and missing features because they see potential value. For TSI, this might be tech-savvy theatre-goers eager for a better ticket-buying experience or venue partners open to experimenting with bulk purchasing.
Growth stage: The product gains traction and reaches a broader audience. Early majority users come on board, expecting reliability and smoother experiences. Competitors notice and intensify their efforts. TSI will now face customers who compare their offering against incumbents, requiring robust features and customer support.
Maturity stage: Market penetration peaks. Users are mainstream customers demanding stability, consistent pricing, and comprehensive service. Differentiation shifts from features to cost efficiency and brand loyalty. TSI must optimize operations, reduce costs, and fend off commoditization.
Decline stage: The product loses relevance due to market shifts or new technologies. Users dwindle, often switching to alternatives. TSI would need to innovate or pivot to avoid this fate.
Understanding these stages helps you anticipate user expectations and tailor your product and marketing strategies accordingly.
User groups mapped to TSI’s product life cycle
| PLC Stage | User Group Characteristics | TSI Example |
|---|---|---|
| Introduction | Innovators and early adopters, risk-tolerant | Tech-savvy theatre-goers, venue partners testing bulk purchase model |
| Growth | Early majority, expect reliable and improved UX | Wider ticket buyers valuing speed and no service fees |
| Maturity | Late majority, price-sensitive, brand loyal | Regular customers seeking stable pricing and availability |
| Decline | Laggards, reluctant to change, switching away | Users moving to newer platforms or direct box office purchases |
This segmentation is not static. User needs evolve with product maturity, and your product roadmap must reflect this.
Choosing the right SDLC for TSI’s stage and context
The software development lifecycle (SDLC) defines how your product moves from concept to delivery and maintenance. Selecting the right SDLC method is critical for managing risk, speed, and quality.
TSI is a seed-funded startup entering a market with entrenched competitors. The initial technology assessment is positive, but the product is unproven. Here is how SDLC choices align with TSI’s needs:
Waterfall: Linear and rigid
Waterfall is a sequential process—requirements, design, implementation, testing, deployment. It suits projects with well-defined, stable requirements.
Why not Waterfall for TSI? At seed stage, assumptions about user demand, pricing, and features are unvalidated. Waterfall’s rigidity makes it costly to pivot. If TSI’s bulk purchase model or distribution network needs changes, delays and rework will mount.
Agile: Iterative and flexible
Agile breaks development into sprints with continuous feedback and incremental delivery. It embraces change and adapts to evolving understanding.
Why Agile fits TSI: At introduction and growth stages, TSI must learn rapidly from customers and adapt features. Agile enables releasing minimum viable products (MVPs), gathering user feedback, and iterating quickly. It supports experimentation with pricing, inventory management, and user experience.
Lean Startup: Build-Measure-Learn loop
Lean Startup methodology focuses on validated learning through rapid experiments and MVPs to test hypotheses before scaling.
Why Lean complements Agile for TSI: Lean’s emphasis on customer discovery and pivoting aligns with TSI’s early phase. Bulk purchasing assumptions can be tested with small venue partnerships before full rollout. Lean encourages avoiding waste by building only what users need.
DevOps: Continuous integration and deployment
DevOps integrates development and operations for rapid, reliable releases and monitoring in production.
Why DevOps is a later-stage fit: TSI will benefit from DevOps once it reaches growth and maturity stages with stable features and a need for operational excellence and scalability.
Recommended SDLC approach for TSI
At seed and introduction stages, Agile combined with Lean Startup principles offers the best balance of speed, flexibility, and learning. TSI can release an MVP of its ticketing platform, test bulk purchase assumptions with select venues, and iterate based on real sales data.
As TSI moves into growth, it can strengthen Agile practices and introduce DevOps for reliability. Waterfall is generally not advised in a startup context due to inflexibility.
The S-Curve pattern and TSI’s innovation trajectory
The S-Curve model of innovation describes technology adoption and performance improvement over time. Early progress is slow (introduction), then rapid (growth), then plateaus (maturity).
TSI’s bulk purchasing and real-time distribution network represent an innovation that might follow this pattern. Initially, customer acquisition will be slow as the market learns the value. Once TSI proves its model, growth can accelerate rapidly. Eventually, competitors may catch up, and TSI will need to innovate further or optimize costs.
Recognizing the S-Curve helps you plan product investments and manage stakeholder expectations.
Summary of your product management approach at TSI
- Use the product life cycle to segment users and anticipate changing needs.
- Apply Agile and Lean Startup methods to build, test, and iterate your MVP quickly.
- Understand your innovation’s place on the S-Curve to time investments and growth initiatives.
- Prepare to evolve your SDLC approach as TSI matures, adding DevOps and process rigor.
This is what week one looks like for most new PMs at startups like TSI: balancing customer discovery, technology validation, and choosing the right development process.
Test yourself: TSI’s product launch and SDLC choice
You are the PM at TSI, a seed-funded startup entering the NYC ticket sales market with a bulk purchase model. You have just completed initial technology and marketing feasibility studies and are planning your product development approach.
The call: Which user groups will you prioritize in the introduction and growth stages? Which SDLC method will you recommend to your engineering lead, and why?
Your reasoning:
Where to go next
- If you want to master product discovery and validation: Discovery & Requirements Definition
- If you want to design effective business models: Business Model Design
- If you want to lead cross-functional teams: Structure, People, and Process in Product Management
- If you want to plan product launches: Taking Products to Market
- If you want to understand the product lifecycle deeply: Product Thinking