---
title: Adava Care Blog Content Pending
type: article
created: '2026-01-22'
updated: '2026-01-22'
source_docs:
- raw/2026-01-22-sprint-planning-meeting-116396706.md
tags:
- adava-care
- blog
- content
- blocker
- gavin
- sebastian
layer: 2
client_source: Adava Care
industry_context: healthcare
transferable: false
---

# Adava Care Blog Content Pending

## Overview

As of the January 22, 2026 sprint planning meeting, Sebastian is blocked on blog work for Adava Care while awaiting content from Gavin. No movement had been made on the blog tasks at the time of the meeting, and Sebastian had already attempted to follow up via activity notifications without success.

## Status

**Blocked** — awaiting blog content from Gavin before build can proceed.

## Details

Sebastian handed blog tasks off to Gavin but received no response or content delivery. During the sprint planning meeting, Sebastian noted he had pinged Gavin again and hoped the notification was received.

Melissa suggested that if Slack/activity pings continue to go unanswered, escalating via email and tagging Mark is the recommended last-resort approach to get a response.

> *"Usually an email tagging Mark is a good way to get him to respond. But I hate doing that — that's my last resort."*
> — Melissa Cusumano, sprint planning 2026-01-22

## Action Items

| Owner | Action |
|---|---|
| Gavin | Deliver blog content to Sebastian for Adava Care |
| Sebastian | Follow up with Gavin via Slack; escalate to email (cc Mark) if no response |

## Related

- [[wiki/meetings/2026-01-22-sprint-planning]]
- [[wiki/clients/current/adava-care/_index]]