Constraints & Requirements

Every problem exists within boundaries. You never have unlimited time, unlimited money, unlimited space, or unlimited flexibility. Constraints are the boundaries that shape what solutions are possible. Requirements are the conditions that a solution must satisfy. Understanding both is essential to finding solutions that actually work in the real world.

What Are Constraints?

A constraint is a limitation you cannot (or choose not to) change. It is a fixed boundary within which you must operate.

Think about planning a dinner party:

Constraints:
  - Budget: $200 maximum
  - Space: Your apartment fits 8 people comfortably
  - Time: The party is this Saturday (3 days to prepare)
  - Dietary: Two guests are vegetarian, one is gluten-free
  - Equipment: You have one oven and a 4-burner stove

These constraints are not problems to solve — they are facts to work within. You cannot make your apartment bigger by Saturday. You cannot change your guests' dietary needs. A good plan works within these boundaries rather than ignoring them.

What Are Requirements?

Requirements are conditions that the solution must meet to be acceptable. If constraints are the walls of the room, requirements are the furniture that must fit inside.

For the dinner party:

Requirements:
  - Serve a full meal (appetizer, main course, dessert)
  - All guests must have options they can eat
  - Food should be ready by 7 PM
  - The meal should feel special (not just ordering pizza)

A solution that violates a constraint is impossible. A solution that fails a requirement is possible but unacceptable.

Everyday Constraints & Requirements

Planning a Vacation

Constraints:
  - Budget: $3,000 for the whole trip
  - Duration: 7 days (limited by work schedule)
  - Travel: One family member is afraid of flying
  - Timing: Must be during school break (March 15-22)

Requirements:
  - Destination should be warm (above 70°F)
  - Activities suitable for children ages 6 and 10
  - Accommodation with a kitchen (to save on meals)
  - No more than 8 hours of driving from home

These constraints and requirements together narrow the options dramatically. Instead of "anywhere in the world," you are now looking at drivable warm destinations within budget during a specific week. That is far more actionable.

Buying a Car

Constraints:
  - Budget: $25,000 maximum
  - Parking: Must fit in a standard garage space
  - Family: Need to fit two car seats in the back

Requirements:
  - Fuel efficiency: at least 30 MPG
  - Safety rating: 4 stars or higher
  - Cargo space: large enough for a stroller and groceries
  - Reliability: brand with a good track record

Building a House

Constraints:
  - Lot size: 50 x 100 feet
  - Zoning: maximum 2 stories, 10-foot setback from property lines
  - Budget: $350,000
  - Timeline: must be complete before winter (8 months)
  - Soil: clay-heavy (affects foundation design)

Requirements:
  - 3 bedrooms, 2 bathrooms minimum
  - Open-plan kitchen and living area
  - Attached garage
  - Energy-efficient (targeting a specific efficiency rating)

The lot size and zoning are hard constraints — physical and legal limits. The budget is a firm constraint. The requirements describe what the house must have to satisfy the homeowner.

Types of Constraints

Hard Constraints

These cannot be violated under any circumstances.

- Laws and regulations (building codes, data privacy laws)
- Physical limits (speed of light, available space)
- Deadlines imposed by external events (tax day, product launch)
- Budget that literally cannot be exceeded

Soft Constraints

These have some flexibility. You would prefer to stay within them, but there is room to negotiate.

- Preferred budget (could stretch 10% if needed)
- Ideal timeline (could push back a week)
- Team preferences (would like to use a specific technology but open to
  alternatives)

Knowing which constraints are hard and which are soft is critical. Treating a soft constraint as hard unnecessarily limits your options. Treating a hard constraint as soft leads to plans that fail.

Constraints in Technology

Performance Requirements

- The page must load in under 3 seconds
- The system must handle 10,000 concurrent users
- The database must support 1 million records
- Backup and recovery must complete within 4 hours

These are measurable and testable. They define the minimum acceptable performance.

Regulatory Constraints

- User data must be stored in the European Union (GDPR)
- Financial transactions must be logged for 7 years
- Healthcare data must be encrypted at rest and in transit
- Accessibility standards (WCAG 2.1 AA) must be met

Regulatory constraints are hard constraints — violating them has legal consequences.

API Rate Limits

Many external services impose constraints on how often you can call them:

- Weather API: 100 requests per hour
- Payment processor: 50 transactions per second
- Email service: 500 emails per day on the free tier

Your system must work within these limits or find alternatives (caching, queuing, upgrading to a paid tier).

How Constraints Help

Constraints feel limiting, but they actually help in several ways:

They narrow the search space

Without constraints, the number of possible solutions is overwhelming. "Design a house" is paralyzing. "Design a 3-bedroom house on a 50x100 lot for under $350,000" gives you a starting point and a direction.

They drive creativity

Some of the best solutions come from working within tight constraints. When you cannot throw money at a problem, you find clever alternatives. When you have limited time, you focus on what matters most.

They prevent scope creep

Requirements define what "done" looks like. Without them, projects expand indefinitely. Clear requirements let you say "this is in scope" and "this is not," and they make evaluation objective rather than subjective.

Documenting Constraints & Requirements

Write them down. Constraints and requirements that live only in people's heads lead to misunderstandings, forgotten conditions, and arguments about what was agreed upon.

A simple format:

Project: Online Order Tracking System

Hard Constraints:
  - Must launch by June 1
  - Budget: $50,000
  - Must integrate with existing order database
  - Must comply with company security policies

Soft Constraints:
  - Prefer to use the team's current technology stack
  - Would like to reuse existing UI components

Requirements:
  - Customer can view order status by entering order number
  - Status updates within 1 hour of actual status change
  - Page loads in under 3 seconds on mobile
  - Available 99.9% of the time (less than 9 hours downtime per year)
  - Supports English and Spanish

Out of scope:
  - Customer account creation (use existing system)
  - Modifying orders (separate project)
  - Analytics dashboard (phase 2)

Conflicting Constraints

Sometimes constraints conflict with each other:

"Make it fast, cheap, and high quality."

The classic project management triangle: you can usually have two of the three, but not all three.

Fast + Cheap    = Lower quality (cutting corners to save time and money)
Fast + Quality  = Expensive (hiring more people, paying for premium tools)
Cheap + Quality = Slow (taking time to do it right with limited resources)

When constraints conflict, someone must decide which ones have priority. Making that decision explicit prevents problems later.

Constraints are boundaries you must work within. Requirements are conditions your solution must satisfy.
Constraints can be hard (inflexible) or soft (negotiable). Knowing the difference is critical.
In everyday life, constraints include budget, time, space, and physical limitations. In technology, they include performance targets, regulations, rate limits, and technical environment.
Constraints help by narrowing options, driving creativity, preventing scope creep, and enabling objective evaluation.
Document constraints and requirements explicitly. Include what is out of scope.
When constraints conflict, make the priority decision explicit rather than leaving it ambiguous.