← Back to the problem

The builder's path

Five steps from a problem to its solution.

For: Tenants in Manitoba can't easily tell whether a proposed rent increase follows the rules, or how to object to it.

“Some things are under our control, while others are not under our control.”
Epictetus · Enchiridion 1 (tr. W. A. Oldfather)

Routes to a solution

Six ways to take this forward

Each route is a different kind of journey, with real people and organisations to contact at each step, starting with those in Manitoba.

  1. Step 1

    Join an incubator or startup mission

    They connect you to schemes and officials.

    • North Forge ↗

      Winnipeg's startup incubator, with a fabrication lab.

    • Futurpreneur ↗

      Startup loans and mentoring for founders aged 18 to 39.

    • Code for Canada ↗

      Civic tech: technologists working with governments on public services.

    • CanadaBuys ↗

      Where the federal government posts its tenders; search by region and category.

  2. Step 2

    Win a seed grant

    Prove the idea works with a small, funded prototype.

  3. Step 3

    Pilot with a public body

    A district, city or department tries it with real people.

    • Code for Canada ↗

      Civic tech: technologists working with governments on public services.

    • CanadaBuys ↗

      Where the federal government posts its tenders; search by region and category.

    • Innovative Solutions Canada ↗

      Federal departments post challenges and fund small businesses to solve them, then buy the result.

    • BDC ↗

      The federal business development bank: loans, advice and venture capital.

What this problem needs

Ideas, sources and tools for this problem, from first interviews to funding.

  • Forms and documents
  • Open data
  • Accessibility

Ideas to explore

  • Idea 1Is my increase allowed?Ask four questions (building age, current rent, proposed increase, notice date), apply the year's guideline and the exemption threshold, and explain the result in plain language with the source rule.
  • Idea 2Object togetherWhen several tenants in one building check the same increase, offer a shared objection letter to the Residential Tenancies Branch they can each sign.

Specific to this problem

Talk to first

  • West Broadway Tenants Committee

    Grassroots renters' group quoted in the article, pushing for the rule changes.

  • Right to Housing Coalition

    One of 50 signatories to the open letter on rent increases.

Starter prompt

Built from this problem's brief. Paste it into Claude or any AI assistant.

Help me design and build a first working prototype for this problem in Winnipeg, Manitoba, Canada.

Problem: Tenants in Manitoba can't easily tell whether a proposed rent increase follows the rules, or how to object to it.
Who it hurts: Renters in Manitoba, especially long-term tenants in older buildings, who receive a notice of a rent increase above the yearly guideline.
The moment it hurts: Opening a landlord's letter that proposes a rise of hundreds of dollars a month, with no explanation of why it is allowed.
What people do today: Tenants rely on advocacy groups and collective letters to the Residential Tenancies Branch, and often don't know whether their unit is covered by rent control at all.
Why it is still unsolved: Whether a unit is covered depends on the building's age and current rent, the guideline changes each year, and landlords can apply for above-guideline increases, so the answer differs unit by unit.
What solved looks like: A free checker where a Manitoba tenant enters their building's age, current rent and proposed increase, and gets a plain answer: whether rent control applies, the guideline for that year, whether an above-guideline application is needed, and how and by when to object, with links to the Residential Tenancies Branch.
Where: Winnipeg, Manitoba, Canada

First, list what you would need to learn from the people affected before building, as interview questions.
Then propose the simplest version that would help, the screens or messages it needs, and the data it would use.
Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.
  1. Understand it

    Talk to the people who live it before you build.

    “Truth is one; the wise speak of it in many ways.”

    एकं सद्विप्रा बहुधा वदन्ति

    ekaṃ sad viprā bahudhā vadanti

    Ṛgveda · 1.164.46
  2. Prototype with AI

    Get a working version in front of people fast.

    Using AI is not cheating. Every tool carries the work of the people who made it, and using it well is how knowledge has always moved forward. The thinking, the care for the people who live the problem, and the judgement are still yours.

    “The Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
    Ada Lovelace · Notes on Menabrea's Sketch of the Analytical Engine, Note A (1843)
  3. Find the data

    Open data that fits this problem.

    “When you know a thing, to hold that you know it; and when you do not know a thing, to allow that you do not know it: this is knowledge.”
    Confucius · Analects 2.17 (tr. J. Legge)
  4. Build it

    Tools matched to what this problem needs.

    “Act, keeping in view the welfare of the world.”

    लोकसंग्रहमेवापि सम्पश्यन्कर्तुमर्हसि

    lokasaṅgraham evāpi sampaśyan kartum arhasi

    Bhagavad Gītā · 3.20
  5. Launch and get support

    Ship it responsibly, and find help and funding.

    “Give me a place to stand, and I will move the earth.”

    δός μοι πᾶ στῶ καὶ τὰν γᾶν κινάσω

    Archimedes · as reported by Pappus of Alexandria

Kit written for this problem from its brief; every link was checked. Links go to each provider's own site. Zetema is not paid for any listing.