Stability, Capability, Participation, Guidance

The product started with a hard question: how do you reduce avoidable conflict in shared housing before it erupts into relocations, mediation time and stress?

That question is still right. It is simply no longer the whole question.

Once the product began serving housing staff, Sozialarbeit, Jobcoach and Freiwilligenarbeit in one operational surface, a housing-only frame became too narrow for what the software was actually doing. A placement can be excellent and still fail to support integration if nobody sees the person's next language step, qualification path, voluntary engagement, or unanswered message. Stable housing is the base layer, not the final outcome.

So the product now needs a broader but still disciplined model:

• Stability: housing, safety, incidents, transfers, rules
• Capability: language, courses, qualifications, work readiness
• Participation: volunteering, community activity, social contact, everyday orientation
• Guidance: staff coordination, follow-ups, next-step planning, message loops

Why these four

The point is not to invent a slogan. The point is to stop building features that live in the product without living in a coherent theory of what the product is for.

The Swiss integration context already points in this direction. The Integrationsagenda Schweiz stresses early information, language acquisition, continuous specialist support, labour-market preparation and familiarity with life in Switzerland. The Federal Statistical Office's integration indicators spread far beyond housing into language, education, labour market, health and participation. European integration monitoring follows the same pattern.

If the product serves those workflows, the research base has to cover them too.

Why housing still stays first

This is not a move away from housing science. It is a move away from pretending housing is enough.

Someone cannot meaningfully progress in work, language or participation when their living situation is unstable, conflicts are unmanaged, or staff time is burned on preventable operational noise. That is why Stability stays first. It is the condition that makes the other three pillars usable.

What changes in the product

This framing forces a more honest product standard.

An item in the system should not be there just because it is possible to store it. It should matter because it contributes to one of the four pillars and leads to an action.

That means:

• incidents should feed back into matching, transfers and follow-ups
• learning records should not die as archive rows; they should drive next steps
• volunteering should appear as visible participation evidence, not an afterthought
• messaging should close loops, not merely exist as a thread
• boards should be shaped by role and intent, not by database tables

What does not change

No black-box "integration score".

The product can track state, progress and unresolved work. It can show evidence. It can help staff prioritise. It can make the next step clearer.

It should not pretend to produce one scalar truth about how "integrated" a person is. That would be conceptually weak, operationally misleading and dangerous in a context involving vulnerable people.

The practical effect

The value proposition becomes stronger:

• for housing staff: fewer preventable disruptions
• for Sozialarbeit: clearer resident progress and follow-through
• for Jobcoach: visible capability and work-readiness evidence
• for volunteering and community roles: participation is no longer invisible
• for residents: clearer pathways, clearer communication, less fragmentation

The product is still rooted in reality. It just now matches the full reality of what the staff are trying to do.