Four-Week Recognition Cycle | Anup Kumar Chandrakumaran

Four-week recognition cycle with period close and reset — Weekly recognition accumulates throughout the period; historical results remain after a new period begins.

The four-week recognition cycle

Week 1

Daily capture, review and Sunday evaluation.

Week 2

Continue the cycle and accumulate results.

Week 3

Patterns across contributions start to emerge.

Week 4

Final evaluation and period close.

Generate the final leaderboard and manager recognition review.
Close the recognition period and preserve its history.
Create the next period; current stars begin from zero.

Reset does not mean delete. Historical stars remain available for reporting, audit and better team conversations.

What if Azure DevOps is not available?

The same idea could be implemented as a dedicated web application. The trade-off should be explicit: Azure DevOps already provides identity integration, permissions, task management, attachments, comments, work history, links and query capability. A custom application gives complete UX control, first-class recognition workflows, richer manager dashboards, built-in learning-session workflows and custom integrations—but the organisation must own and support another application.

Azure DevOps-based approach	Dedicated application
Use an established system of work with lower operational ownership.	Build a tailored contribution and learning experience with higher ownership.
Recognition is a supporting layer.	Recognition and learning workflows can be first-class features.

Explore a standalone alternative

TeamContributionHub is an interactive concept showing how daily work capture, manager review, reporting and a four-week recognition cycle could come together when Azure DevOps is unavailable.

Explore the interactive prototype (opens in a new tab) →

The demo uses sample data and simulated actions. No account is required, file uploads are disabled, and comments and cycle changes reset when the page reloads.

The product opportunity

A platform that makes invisible work visible, turns recognition into shared learning, and gives managers a broader view of team contribution without reducing people to ticket counts.

The opportunity is not another task tracker. It is a focused layer for contribution intelligence, recognition evidence, learning workflows and continuous improvement.