Tenant Interview Script¶
Date: 2026-06-25
Status: Accepted Product Owner interview script for EP10-T3.
Related charter: Pre-release charter
Related pilot ops: Founding pilot ops
Related backlog: Pre-release delivery epics
Purpose¶
This script validates which tenant tasks help or block landlord value in the first paid pilot.
The tenant is not the first economic buyer, but MamNajem depends on tenants for selected workflows: invite acceptance, document access, handover confirmation, payment proof, issue reporting, and final settlement or deposit review. The interview should identify which of those tasks tenants will actually complete and which ones create distrust or friction.
Target Participant¶
Prioritize tenants who:
- live in or recently lived in a long-term residential rental in Poland
- dealt directly with a self-managing landlord, or can clearly describe the owner/manager relationship
- moved in, moved out, paid rent, reported an issue, or discussed deposit return in the last 12 months
- can show or describe recent rental artifacts without exposing unnecessary personal data
Good sample mix:
- tenants referred by accepted pilot landlords
- tenants who moved in or out recently
- tenants who recently had a payment, repair, document, or deposit discussion
- a few independent tenants from major-city rental communities, so the sample is not limited to highly organized landlords
Interview Setup¶
Recommended length: 35-40 minutes.
Suggested structure:
| Segment | Time |
|---|---|
| Opening and consent | 3 minutes |
| Rental context and recent episode | 5 minutes |
| Tenant workflow walkthroughs | 20 minutes |
| App adoption and rejection test | 8 minutes |
| Closeout and pilot task | 4 minutes |
Do not request copies of tenant IDs, full contracts, bank statements, landlord private data, signatures, PESEL/ID numbers, bank account details, or full address details. Screen-share or verbal walkthrough is enough. Ask the tenant to redact or hide sensitive fields.
Prep Note¶
Send this before the call.
Thanks for agreeing to speak with us.
This is a practical interview about renting workflows, not an evaluation of you
or your landlord. If you are comfortable, please have a few recent examples
ready to screen-share:
- where you keep or find your rental documents
- the last handover, meter-reading, inventory, or photo record you received
- a recent rent payment reminder, payment proof, or receipt
- a recent issue or repair message
- any move-out, final settlement, or deposit discussion
You do not need to send files in advance. Please hide tenant personal data,
bank details, ID numbers, signatures, and addresses that are not needed for the
workflow discussion.
Opening Script¶
Use this at the start.
I am not evaluating you, and I am not here to represent your landlord. I want to
understand how communication, payments, documents, handovers, repairs, and
deposit discussions actually work from the tenant side.
Please skip or hide anything sensitive. I am interested in the workflow: where
information lives, what is easy, what is confusing, and what you would or would
not do inside a landlord-invited app.
Fit Screen¶
Ask these first.
| Question | Capture |
|---|---|
| What kind of rental are you in now or were you in most recently: room, studio, apartment, or house? | Rental type. |
| Was it long-term residential rental? | Fit. |
| Did you deal directly with the owner, an agency, or a manager? | Relationship and adoption context. |
| Did you move in, move out, report an issue, pay rent, or discuss a deposit in the last 12 months? | Recency. |
| Which channel did you use most with the landlord: WhatsApp, SMS, phone, email, app, or something else? | Current channel. |
Workflow Walkthrough¶
Use this table as the core script. Ask for recent examples instead of general opinions.
| Block | Exact prompt | Proof to request | Capture |
|---|---|---|---|
| Document access | Where do you find your contract, annexes, house rules, handover protocol, meter readings, or other rental documents today? What happens when you need them later? | Email, PDF folder, chat attachment, paper copy, cloud folder. | Whether document access is easy, scattered, or landlord-dependent. |
| Move-in or handover confirmation | Tell me about your last move-in or move-out. How were condition, photos, meter readings, keys, and inventory confirmed? | Protocol, photos, meter readings, inventory list, chat confirmation. | Whether tenant understood what they confirmed and whether evidence was retrievable. |
| Payment proof | How do you know what amount to pay, when to pay, and whether the landlord recognized the payment? Show the last proof, reminder, receipt, or message if you can. | Bank transfer confirmation, screenshot, reminder, receipt, rent message. | Whether payment proof is manual, trusted, duplicated, or unclear. |
| Issue reporting | Tell me about the last issue or repair. How did you report it, share photos, get status updates, and know what was agreed? | Chat thread, photos, email, invoice/update message. | Whether in-app issue reporting would help or feel unnecessary. |
| Final settlement and deposit | If you moved out or discussed deposit return, how were deductions, deadlines, photos, and final amounts explained? | Settlement note, message thread, photos, invoice, bank transfer. | Whether deposit transparency would reduce conflict or mistrust. |
| Communication | Show or describe one normal landlord thread and one confusing or stressful thread. Where did decisions and attachments end up? | WhatsApp, SMS, email, phone notes. | Whether tenant wants a structured record or prefers existing chat. |
App Adoption Test¶
Ask after the workflow walkthrough.
If your landlord invited you to one app for documents, handover confirmation,
payment proof, issue reporting, messages, and final settlement, which tasks
would you actually complete there and which would you ignore?
Use this task list:
| Tenant task | Response |
|---|---|
| Accept invitation and open lease workspace | yes / maybe / no |
| View contract, annexes, and handover documents | yes / maybe / no |
| Confirm move-in or move-out handover details | yes / maybe / no |
| Upload or mark payment proof | yes / maybe / no |
| Report a simple issue with text and photos | yes / maybe / no |
| Read landlord messages and reminders | yes / maybe / no |
| Review final settlement or deposit deductions | yes / maybe / no |
| Acknowledge receipt of settlement or deposit explanation | yes / maybe / no |
For every maybe or no, ask:
What would block you from doing that in the app?
Capture whether the block is about privacy, trust, duplicate work, tenant value, landlord relationship, extra fees, app fatigue, legal concern, language, or accessibility.
Rejection Test¶
Ask directly:
What would make you reject a landlord-invited rental app?
Then probe:
- Would it feel helpful, neutral, or like landlord control?
- Would you use it if it gave you clearer documents and payment proof?
- Would you use it if it helped protect handover photos and deposit evidence?
- Would you reject it if the landlord still used WhatsApp for everything?
- Would you reject it if there were tenant fees?
- What data would you refuse to upload?
Capture the tenant's exact words for any strong rejection.
Pilot Task Test¶
Ask:
If your landlord was already in a 90-day pilot, would you complete one real
task in the app, such as confirming a handover, viewing a document, uploading
payment proof, reporting an issue with a photo, or reviewing a deposit
settlement?
If yes:
- Which task would you complete first?
- What would make it feel safe and useful?
- Would you do it on mobile only?
If maybe:
- What proof or explanation would you need first?
- Would a landlord message be enough, or would you need MamNajem to explain why the app exists?
If no:
- What exact concern blocks you?
- Would any task be acceptable, or would you refuse the app entirely?
Adoption Blocker Taxonomy¶
Use one primary blocker and one optional secondary blocker.
| Blocker | Use when |
|---|---|
privacy_or_surveillance |
Tenant sees the app as monitoring, landlord control, or excessive data collection. |
no_tenant_value |
Tenant sees no clear benefit for themselves. |
duplicate_channel |
Tenant would use WhatsApp/email anyway and sees the app as duplicate work. |
app_fatigue |
Tenant resists installing or learning another app. |
payment_trust |
Tenant is worried payment proof, status, or recognition will be unclear. |
document_sensitivity |
Tenant refuses to upload or view sensitive rental documents in the app. |
landlord_relationship |
Tenant adoption depends on trust in the specific landlord. |
legal_confusion |
Tenant is unsure whether app confirmation has legal effect. |
fee_rejection |
Tenant rejects any tenant-side fee. |
language_or_accessibility |
Tenant cannot comfortably use the language, device, or interface. |
low_recency |
Tenant has no recent workflow memory, so the interview gives weak signal. |
not_relevant |
Tenant is outside the target rental situation. |
Tenant Notes Template¶
Copy this for every interview.
Interview ID:
Date:
Interviewer:
Tenant source: pilot landlord / independent / referral / other
Rental type:
City:
Direct owner / agency / manager:
Recent event:
Primary communication channel:
Artifacts or examples shown:
- document access:
- handover confirmation:
- payment proof:
- issue reporting:
- final settlement/deposit:
- communication thread:
Tasks tenant would complete:
- invitation:
- document view:
- handover confirmation:
- payment proof:
- issue report:
- messages/reminders:
- settlement/deposit review:
- settlement/deposit acknowledgment:
Tasks tenant would ignore:
Strongest tenant-side value:
Strongest tenant-side concern:
Exact rejection quote:
Primary blocker code:
Secondary blocker code:
Pilot task willingness: yes / maybe / no
First acceptable pilot task:
What explanation tenant needs:
Landlord value impact:
Decision:
Next action:
Landlord Value Interpretation¶
After the interview, classify tenant adoption risk:
| Classification | Criteria | What it means for landlord value |
|---|---|---|
| Strong adoption signal | Tenant would complete at least three launch tasks and can name personal value. | Tenant-side workflows can support landlord activation. |
| Minimal viable adoption | Tenant would complete one or two concrete tasks if invited by a trusted landlord. | Keep tenant surface narrow and task-specific. |
| Blocked adoption | Tenant rejects the app, sees it as control, or refuses the tasks needed for landlord value. | Owner-only activation must carry value, or tenant UX/copy needs narrowing. |
| Weak evidence | Tenant has no recent relevant workflow or cannot recall specifics. | Do not use this interview as adoption proof. |
Tenant tasks that can block landlord value:
- tenant ignores invitation
- tenant cannot find or understand documents
- tenant refuses handover confirmation
- tenant will not upload payment proof when needed
- tenant reports issues outside the app after agreeing to use it
- tenant does not review final settlement or deposit explanation
- tenant sees the app as surveillance rather than transparency
Evidence¶
EP10-T3 is complete because this script asks tenants about document access, handover confirmation, payment proof, issue reporting, final settlement/deposit discussion, and which tasks they would actually complete in an app. It also gives the interviewer a blocker taxonomy and notes template for deciding which tenant tasks block landlord value.
Source records: