Defining Functional Requirements for a Goal-Oriented Feedback Community

Problem Context

In many online communities, users share work, ideas, or early-stage projects in order to receive feedback from others. However, this feedback is often informal, subjective, and difficult to translate into clear next steps. This problem is especially visible in communities where users share unfinished work and need feedback on a specific aspect rather than general opinion.

Problem Analysis

The core issue is not the absence of feedback, but the absence of context. When reviewers do not understand the poster’s intended goal, feedback often becomes irrelevant, superficial, or overly general. For example, someone seeking feedback on navigation clarity may instead receive comments about visual style. This mismatch reduces the usefulness of feedback and makes it harder for users to identify actionable improvements.

Proposed Solution

This project proposes a lightweight community hub where users can share work-in-progress and request structured, goal-oriented feedback from others. Instead of posting for general opinion, users are required to define a clear feedback goal, and reviewers respond through guided prompts aligned with that goal.

This approach transforms feedback from free-form commentary into a more focused and actionable interaction process. In design-related cases, this approach can also support lightweight usability testing, but the system is intended to support a broader range of goal-oriented feedback scenarios.

Functional Requirements

Core Requirements

• The system must require users to define a clear feedback goal when creating a post. This is essential because the community is intended to support focused, goal-oriented feedback rather than general opinion. Without this requirement, feedback is likely to become vague and misaligned.
• The system must display each post together with its associated feedback goal. This allows other community members to quickly understand the context of the post and decide whether they are able to contribute useful input.
• The system must guide reviewers to provide structured feedback through predefined prompts such as clarity, confusion, and suggestions. This requirement is necessary to improve the relevance and actionability of responses, especially in situations where users are sharing unfinished or exploratory work.
• The system must display feedback in relation to the original goal rather than as isolated comments. This helps the poster interpret responses more effectively and supports more meaningful revision or iteration.

Optional Features

Optional features may include filtering feedback by category or supporting different posting contexts, such as early concepts, polished drafts, or non-design project ideas. While these could improve usability and flexibility, they are not essential to demonstrating the core concept of structured, goal-oriented feedback.

Scope Decisions

Advanced features such as expert matching, reputation systems, or automated analysis are intentionally excluded in order to maintain a focused and achievable scope. While these features may add value in a real-world platform, they are not necessary to demonstrate the core interaction model of structured feedback within a social community.

Alternative Approaches

One alternative would be to allow completely free-form feedback, which would reduce friction and make participation easier. However, in a community setting, this would likely encourage short, low-effort responses that are only loosely connected to the poster’s goal. Another alternative would be automated or AI-generated feedback, which might provide consistency but would introduce technical complexity and reduce the value of human perspectives within the community. For this reason, structured peer feedback offers a more balanced solution.

Trade-offs

Structured feedback improves relevance and actionability, but it also reduces flexibility in how users respond. Requiring users to define a feedback goal increases clarity, but also adds friction to the posting process. These trade-offs are acceptable because the system prioritises meaningful, goal-oriented interaction over open-ended social commentary.

Technical Alignment

Structured input fields directly support the functional requirement of improving feedback relevance. By constraining responses around the stated goal, the system reduces misalignment and makes feedback easier to organise, compare, and interpret. This also supports a clearer interaction model, as posts, goals, and responses can be presented as related parts of the same feedback process rather than as disconnected comments.

Evaluation and Responsibility

The system can be evaluated by examining whether users produce feedback that is more relevant, goal-aligned, and actionable than in unstructured comment systems. It is also important to assess whether the added structure improves feedback quality without discouraging participation. Accessibility considerations include proper labelling, keyboard navigation, and clear hierarchy. In addition, the platform should encourage respectful and constructive feedback in order to reduce the risk of dismissive, overly personal, or unhelpful comments.

Conclusion

By embedding structured, goal-oriented feedback into a community setting, this system aims to improve the quality and usefulness of peer responses for users sharing work, ideas, or projects in progress.