Sunday League Hub

I turned the insights into product rules, so the screens follow from the research rather than being a collection of isolated ideas:

• Attendance is separate from discipline: a late cancellation is flagged for review, never fined automatically
• Proposed fines are separate from approved obligations
• Recording a payment doesn't mean it's verified; each payment shows its verification state
• Players can dispute a fine, and the resolution is recorded
• Role-based access: players see their own finances, officers manage records within their responsibilities
• Community activities are mandatory or optional, with deadlines, assignments, attendance and completion
• The home screen puts outstanding actions first: the next match, fines to answer, payments, community duties
• Important status changes keep an audit history, so records can be checked when questions come up
• It runs as a Telegram Mini App, because the team already lives in Telegram
• Teams are picked at the pitch after check-in, not in advance: no-shows and players who turn up without answering would break a list made the day before
• Match day follows the team's own rules: 10-minute matches, first to 2 goals or the leader at 10:00 stays on, a coin flip for a draw, and a number call to decide who sits out and who fills a short team
• Ref mode runs on the organiser's phone, which the waiting players hold: the score, the 05:00 keeper change, photos and late arrivals

I structured a task-based evaluation around realistic team scenarios. Each one can be completed in the prototype:

• Confirm attendance for an upcoming Sunday match
• Change an answer and see whether it falls inside the 24-hour cancellation window
• Review an outstanding balance and how it was calculated
• Record a payment and check its verification status
• Review a proposed fine and submit a dispute
• Find a mandatory community activity, its deadline and assigned responsibilities
• Review the history of a record to see who changed its status
• Check in at the pitch, add someone who turned up without answering, and pick teams
• Run a match as the ref: keep score, settle a draw with the coin flip and call a number for who comes on

I also reviewed version 2 against Nielsen's 10 heuristics myself. Fixed:

• Payments now show "waiting for Dawit to verify" until they're checked
• Check-in can be changed freely until the deadline, and every change is timestamped
• An exception can't be sent without proof, and a dispute can't be sent without an explanation
• Fine reasons come from a fixed list instead of free text
• Reminders now show the message and who gets it before they're sent
• Still open: accepted fines can't be undone, and officers can fine themselves

The next round of evaluation focuses on these questions and edge cases:

• Do players understand the attendance and cancellation rules?
• Is the financial information transparent enough?
• Does the dispute process feel fair?
• Are mandatory community activities easy to find and manage?
• Can the ref keep score and run the number call with the phone in one hand, between matches?
• Edge cases: duplicate payment records, unverified transactions, disputed fines, unauthorised edits, attendance changes after the deadline, no-shows, late arrivals and fewer than 10 at the pitch

Measures for testing with the team, and targets for a pilot. None of these have been measured yet.

• Task completion, errors and time on task for each evaluation scenario
• Whether players can explain the cancellation, fine and dispute rules after using the app
• 80% of the squad answers before the deadline by week 4
• No fine disputes because someone didn't know
• 90% of payments verified within 48 hours