---
title: User Story Resources
---

:::caution[Programme Sunset]
The open Mentorship Programme has been sunset and is no longer accepting new participants. These pages remain available as reference material.

I'm now running a private, personalised professional development programme on an invite-only basis - hand-selecting a small number of participants so the shape of each journey can be built around them. There is no application process; participation is by direct invitation only.

Being active in my [Discord community](https://chat.nhcarrigan.com/) increases your chances of being invited.
:::

**USER STORY TEMPLATES, EXAMPLES, AND WRITING GUIDES**

## User Story Format

### Standard Format

```
As a [user type], I want [goal/desire] so that [benefit/value].
```

### Components

- **User Type:** Who is the user? (e.g., authenticated user, admin, guest)
- **Goal/Desire:** What do they want to do?
- **Benefit/Value:** Why do they want this? What value does it provide?

## User Story Examples

### Authentication Examples

**Example 1:**
As an unauthenticated user, I can create an account so that I can access personalized features.

**Example 2:**
As an unauthenticated user, I can sign in to my existing account so that I can access my saved data.

**Example 3:**
As an authenticated user, I can sign out so that I can secure my account when using shared devices.

### Profile Management Examples

**Example 1:**
As an authenticated user, I can view my profile so that I can see my account information.

**Example 2:**
As an authenticated user, I can edit my profile information so that I can keep my details up to date.

**Example 3:**
As an authenticated user, I can upload a profile picture so that others can identify me.

### Content Management Examples

**Example 1:**
As an authenticated user, I can create a new post so that I can share content with others.

**Example 2:**
As an authenticated user, I can edit my own posts so that I can correct mistakes or update information.

**Example 3:**
As an authenticated user, I can delete my own posts so that I can remove content I no longer want to share.

**Example 4:**
As a user, I can view posts from other users so that I can see community content.

### Admin Examples

**Example 1:**
As an administrator, I can review posts for content violations so that I can maintain community standards.

**Example 2:**
As an administrator, I can remove posts that violate policies so that I can keep the community safe.

**Example 3:**
As an administrator, I can view user analytics so that I can understand community engagement.

### Task Management Examples

**Example 1:**
As an authenticated user, I can create a new task so that I can track work that needs to be done.

**Example 2:**
As an authenticated user, I can mark a task as complete so that I can track my progress.

**Example 3:**
As an authenticated user, I can organise tasks into projects so that I can group related work.

**Example 4:**
As an authenticated user, I can set task dependencies so that I can ensure tasks are completed in the correct order.

## User Story Writing Guide

### Step 1: Identify User Types

**Common User Types:**
- Unauthenticated user (guest, visitor)
- Authenticated user (logged-in user)
- Administrator (admin, moderator)
- Premium user (if applicable)
- Specific roles (e.g., teacher, student, manager)

### Step 2: Think About User Goals

**Questions to Ask:**
- What does this user type want to accomplish?
- What actions do they need to take?
- What information do they need to see?
- What features would be valuable to them?

### Step 3: Consider the Value

**Value Considerations:**
- Why is this feature important?
- What problem does it solve?
- How does it improve the user experience?
- What benefit does it provide?

### Step 4: Write the Story

**Writing Tips:**
- Keep it simple and focused
- One feature per story
- Use clear, concise language
- Focus on user value, not implementation

### Step 5: Review and Refine

**Review Checklist:**
- Is the user type clear?
- Is the goal specific and actionable?
- Is the value/benefit clear?
- Is it testable?
- Is it independent (can be developed separately)?

## User Story Template

```markdown
## User Story: [Brief Title]

**As a** [user type]
**I want** [goal/desire]
**So that** [benefit/value]

### Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

### Notes
[Any additional context or considerations]
```

## Common User Story Patterns

### CRUD Operations

**Create:**
As an authenticated user, I can create [resource] so that [value].

**Read/View:**
As a user, I can view [resource] so that [value].

**Update:**
As an authenticated user, I can edit [resource] so that [value].

**Delete:**
As an authenticated user, I can delete [resource] so that [value].

### Authentication Flow

- Account creation
- Sign in
- Sign out
- Password reset
- Email verification
- Profile management

### Content Management

- Create content
- View content
- Edit content
- Delete content
- Search/filter content
- Organise content

### Social Features

- Follow users
- Like/favourite content
- Comment on content
- Share content
- Message users

## Best Practices

### Do's

✅ Write from the user's perspective
✅ Focus on value and benefits
✅ Keep stories independent
✅ Make stories testable
✅ Use clear, simple language

### Don'ts

❌ Include technical implementation details
❌ Combine multiple features
❌ Use vague or ambiguous language
❌ Focus on "how" instead of "what"
❌ Make stories too large or complex

---

*User stories should be clear, focused, and user-centred. They guide development by keeping the focus on user value.*

