Key Decisions

Decision

Use configurable channels as the core structure for discussions.

Context

Customers needed more than a single discussion space. A discussion might need to exist around a particular topic, cohort, group of participants or learning activity.

Why

Research into other LMS and community platforms showed that the channel model was already familiar and flexible. It also aligned with customer needs for separate discussion groups, adapting a pattern users could already understand from products such as Slack.

Trade-off

Channels introduce more structure and configuration than a single feed. Course authors therefore need to understand when and why to create separate spaces.

Outcome

Course authors can create targeted discussion spaces with their own audience and participation rules.

Decision

Create different ways of returning to relevant activity, including Catchup, Mentions & Replies and Bookmarks.

Context

As discussion activity increases, simply providing more content creates another problem: users need to understand what deserves their attention.

Why

Users needed ways to quickly find activity that was meaningful to them, rather than having to work through every conversation.

Trade-off

Multiple discovery mechanisms increase navigation complexity. Each area therefore needed a clear purpose rather than becoming another variation of the same feed.

Outcome

The structure supports different user intents: catching up on activity, returning to direct interactions or saving useful content for later.

Decision

Create a dedicated Manage Posts area covering published and all posts, drafts and scheduled posts.

Context

Users may create multiple posts over time, including content that has not yet been published.

Why

A predictable place for managing personal content supports day-to-day workflows, while scheduling allows communications to be prepared in advance.

Trade-off

This introduces content-management functionality into what could otherwise be treated as a simple discussion experience.

Outcome

Users can manage the lifecycle of their own communication rather than locating individual posts across channels.

Decision

Use Guroo's established permission model rather than inventing a separate permissions system for Discussion Boards.

Context

Course authors, facilitators and learners need different capabilities and should not automatically have identical access to every discussion space or action.

Why

Existing platform rules were familiar to developers and could be captured through user stories while remaining consistent with the broader product.

Trade-off

The experience needs to accommodate multiple combinations of visibility and participation rules, increasing the complexity behind apparently simple UI interactions.

Outcome

Channels can support different learning contexts while remaining aligned with established Guroo product behaviour.

Decision

Introduce reporting and moderation functionality.

Context

Moderation was not part of the original feature concept. As the system evolved from announcements into participatory discussion spaces, inappropriate behaviour also needed to be considered.

Why

A communication platform that allows learners and facilitators to participate needs mechanisms for handling misuse.

Trade-off

Moderation introduces additional states, workflows and responsibilities that do not exist in a simple publishing feature.

Outcome

The concept includes reporting and moderation workflows, making the system more suitable for genuine community participation.