Watnwy

Plan, review, and publish your team’s Technology Radar with collaborative workflows
Rating
Your vote:
No screenshots
Notify me upon availability

Start your next planning cycle by turning scattered tech choices into a living map. In Watnwy, spin up a workspace, set your rings (Adopt, Trial, Assess, Hold) and categories, then seed it with what you already use: paste a list, upload a CSV, or let repo scanning suggest tools, libraries, services, and practices. Each item opens a guided card with three prompts—What it is, Why it matters, Why it’s timely—so contributors capture context fast. Assign an owner, link evidence (PRs, ADRs, benchmarks, incidents), and add tags like domain, risk, and lifecycle. As your team adds entries, Watnwy builds a clear picture of your stack and experiments, organized for action rather than shelf-ware.

Run decisions through a lightweight workflow instead of hallway debates. Proposals start as drafts, move to team review, and optionally to an architecture group for sign‑off. Comment threads stay on the card. Voting and scorecards quantify value, risk, cost, and effort so you can compare options side by side. Set review cadences (monthly, quarterly) and auto‑generate an agenda with items nearing expiry, disputed entries, and high‑impact changes. Notifications flow to Slack or email; follow‑ups can open as Jira issues with one click. When you’re ready, publish a snapshot to a shareable page or embed it in your wiki. Versioning keeps history, making it easy to show how guidance evolved and why a status changed. more

Review Summary

Features

  • - Collaborative editor with templates for What / Why / Why now
  • - Rings, categories, tags, and owners per item
  • - CSV import, repo scanning suggestions, and quick-add forms
  • - Draft → review → approval workflow with comments and mentions
  • - Voting, scorecards, and comparison views
  • - Scheduled reviews, agendas, and notifications (Slack/email)
  • - Jira issue creation from radar items and actions
  • - Versioning, snapshots, and public/private publishing
  • - Dashboards, trends, and heatmaps for adoption tracking
  • - Campaigns with milestones and cross-repo task lists
  • - API access, Git sync, and PR policy checks
  • - SSO, RBAC, and audit trails for compliance
  • - Multi-radar support and organization-wide rollups
  • - Exports to Markdown, CSV, and slides
  • embeddable views
  • - Search, filters, and evidence links (PRs, ADRs, incidents)

How It’s Used

  • - Stand up an internal Technology Radar during a quarterly planning workshop
  • - Evaluate competing tools with scorecards and capture rationale in one place
  • - Track deprecation of legacy libraries and auto-create Jira follow-ups
  • - Launch a cross-team initiative (e.g., Observability standardization) with milestones
  • - Onboard new engineers with curated What/Why/Why-now entries and starter links
  • - Enforce guardrails via PR checks that flag Hold technologies
  • - Publish a public-facing radar to align partners and recruit contributors
  • - Report to leadership using trend analytics and exported slides
  • - Sync radar data with Git and BI tools for governance and forecasting
  • - Capture architecture council decisions with linked ADRs and versioned history

Plans & Pricing

Watnwy

Custom

Capture the context
Propose status updates
Iterate over the rationale document
A built-in peer-reviewing system
A single place to track new versions

Comments

User

Your vote: