Training Module 18 — Feature Requests

GoClubPro User Training | Area: Feature Requests / Suggest Features

---

What Users Need to Learn

The Feature Requests section lets all members contribute ideas for improving GoClubPro. Users need to understand:

• How to submit a feature request
• How to vote on existing requests
• How to add pros/cons to a discussion
• How to track the status of requests
• What the different statuses mean

---

1. Step-by-Step Walkthrough

Submitting a New Feature Request

1. Click Suggest Features in the navigation footer (or go to /features).
2. You land on the Feature Requests page.
3. Before submitting: search existing requests to avoid duplicates.
4. Click + New Request.
5. Fill in:

• Title: A concise description (e.g., "Export fixture schedule to Google Calendar")
• Description: Why this feature would be useful and who it would help
• Screenshot or mockup (optional): Visual illustration of what you have in mind

6. Click Submit — your request is published immediately.

Voting on a Request

1. Browse the Feature Requests list.
2. Click the upvote button (thumbs up / +1) on any request you support.
3. Click again to remove your vote.
4. High vote counts signal to the product team which features matter most.

Adding a Pro or Con

1. Click on any feature request to open the detail view.
2. Scroll to the Discussion section.
3. Click Add Pro or Add Con to contribute to the argument:

• Pro: A reason this feature should be built
• Con: A concern or reason it might not work as described

4. Other members can upvote individual pros and cons.

Tracking Request Status

1. On the Feature Requests list, each request has a status badge:

• Open — submitted, under consideration
• Planned — product team has committed to building it
• In Development — actively being built
• Implemented — shipped and available in the app
• Rejected — won't be built (reason provided)

2. Filter by status to see what's been planned or implemented recently.

---

2. Simple Explanation (Beginners)

The Suggest Features section is a community wishlist. If there's something GoClubPro doesn't do that would make your club's life easier, submit it here.

The product team reads these. High-voted requests get prioritised. If your idea is selected, the status changes from "Open" to "Planned" then "Implemented" — and you'll see your idea in the app.

---

3. Advanced Explanation (Power Users)

Voting weight: All votes are equal — there's no premium or weighted voting. The product team uses vote counts as one signal among many (also considering implementation effort, platform fit, and strategic priorities).

Pros/cons system: This isn't just a voting system — it's a structured debate format. A request with 50 upvotes but a highly-upvoted Con ("This would create GDPR issues") may be deprioritised or redesigned. Contributing thoughtful pros and cons is more useful than just voting.

Duplicate handling: If you submit a request similar to an existing one, a moderator may merge it. Your vote and the merged request's votes are combined. You'll receive a notification if your request is merged.

Status transitions: Only Platform Admin and the product team can change statuses. Status changes trigger notifications to everyone who voted on or commented in the request.

Rejected requests: A rejection includes a reason. Common reasons: "Out of scope", "Technically infeasible", "Conflicts with privacy policy". Rejected requests can be re-opened if circumstances change — add a comment explaining the new context.

---

4. Visual Description (Text-Based)

┌─────────────────────────────────────────────────────────┐
│ FEATURE REQUESTS │
│ │
│ [ + New Request ] [ Filter: All ▼ ] 🔍 Search │
│ │
│ ┌─────────────────────────────────────────────────┐ │
│ │ ⬆ 47 Export schedule to Google Calendar │ │
│ │ Status: PLANNED · 12 comments │ │
│ │ "Add a one-click export so fixtures │ │
│ │ appear in our personal calendars" │ │
│ └─────────────────────────────────────────────────┘ │
│ │
│ ┌─────────────────────────────────────────────────┐ │
│ │ ⬆ 31 Bulk RSVP on behalf of team │ │
│ │ Status: OPEN · 5 comments │ │
│ │ "Coaches need to be able to mark RSVP │ │
│ │ for an entire team at once" │ │
│ └─────────────────────────────────────────────────┘ │
│ │
│ ┌─────────────────────────────────────────────────┐ │
│ │ ⬆ 8 Dark mode UI │ │
│ │ Status: OPEN · 3 comments │ │
│ └─────────────────────────────────────────────────┘ │
│ │
│ ┌─────────────────────────────────────────────────┐ │
│ │ ⬆ 2 Add video uploads to Noticeboard │ │
│ │ Status: REJECTED · Reason: Storage costs │ │
│ └─────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────┘

---

5. Tooltips & Hints

---

6. FAQ — Feature Requests

Q: How long before my request is reviewed? A: The product team reviews new requests weekly. Status updates don't have a guaranteed timeline — popular requests are reviewed sooner.

Q: My request got merged with another one. What happened to my votes? A: Your votes transferred to the merged request. You'll receive a notification explaining the merge.

Q: Can I edit my request after submitting? A: Yes — click your request → Edit. Major changes (fundamentally different scope) should be a new request instead.

Q: Why was my request rejected? A: The rejection reason is provided on the request. Common reasons: out of scope for a sports club platform, too costly to implement for the benefit provided, conflicts with privacy regulations, or depends on a third-party integration that isn't feasible.

Q: Can I request changes to the rejection? A: Add a comment responding to the rejection reason with new information or context. The product team may reconsider if circumstances have changed.

Q: Is there a limit on how many requests I can submit? A: No hard limit, but avoid submitting many low-effort requests. Quality requests with clear use cases are more likely to be acted on.

---

7. Common Mistakes & How to Avoid Them

---

8. Short Onboarding Script

Suggest Features — Your Ideas Shape the App

Got an idea that would make GoClubPro better? Submit it here:

• Search first to see if it's already been suggested
• Click + New Request and describe your idea clearly
• Vote on others' ideas that you support

Highly-voted requests get prioritised. Your idea might be live in a future update.

---

9. Long Training Guide

Writing a Great Feature Request

A well-written request is far more likely to be planned than a vague one.

Good request structure:

• Problem statement: What can't you do today that you wish you could?
• Proposed solution: How would you like it to work?
• Who benefits: Is this for players, coaches, treasurers, everyone?
• How often needed: Is this daily, weekly, once a season?
• Example scenario: Walk through a specific real-world use case.

Example:

Title: Export fixture schedule to Google Calendar / iCal

Description: Currently, players must manually add fixtures to their personal calendars. If GoClubPro generated an .ics file or a calendar subscription URL, fixtures would automatically appear in members' phones.

Who benefits: All members who use a personal calendar.

How often: Once per season to subscribe; updates sync automatically when fixtures change.

Scenario: Sarah gets selected for Saturday's match. She wants it to appear in her iPhone Calendar automatically, including the ground address and fixture time. Right now she has to manually add it.

This level of detail helps the product team design the right solution.

Understanding Priority Signals

The product team weighs:

1. Vote count — broad desire for the feature
2. Pro/con balance — whether there are significant objections
3. Implementation effort — some features are quick; others affect core architecture
4. Strategic fit — does it align with the platform's direction?
5. User type — requests from Treasurers or Club Admins may carry more weight than niche edge cases

The Implemented Status

When a feature you voted for becomes Implemented:

• You receive a notification.
• The feature request is archived (still viewable for reference).
• A link to the relevant part of the app is shown on the request.

It's worth checking Implemented requests periodically — you might find a feature you didn't know existed.

---

10. Micro-Training (Quick Tips)

⚡ QUICK TIPS — Feature Requests

✅ Search before submitting — duplicates get merged anyway
✅ Write a specific, detailed request — vague ones get ignored
✅ Vote on others' ideas you care about
✅ Add thoughtful pros and cons — not just upvotes
✅ Check "Implemented" requests to discover new features
✅ Rejected ≠ forever — add new context and request reconsideration

---

11. Troubleshooting

---

Module 18 of 20+ | Next: Module 19 — End-of-Season Workflow