Tools
The tools I often use across a project , roughly in the order they come up: understanding the problem, planning the product, designing the data, building it, and making sense of what comes back. Knowing which one fits matters more than knowing all of them, and a simpler or open-source option often beats the expensive one. Each is grouped by Adopt, Trial, Assess, or Hold that's adapted from Thoughtworks' Technology Radar to help you evaluate its current state.
Product & researchData & integration
Build & operateAnalytics & GIS
AdoptProduct & research#1
GitHub Projects
This has been my preferred product management tool since it released. Boards span multiple repositories, custom fields go beyond the default issue set, and linking pull requests to issues puts Product and Engineering on the same board.
docs.github.com ↗Adopt17
1GitHub Projects
2Figma
6Miro
7Markdown
12PostgreSQL & MySQL
13MongoDB
14Google Sheets
15Swagger
16Open Data Kit (ODK)
22Open Source BI: Superset or Metabase
23Jupyter Notebooks
24R
26Mapbox
32VS Code
33Frontend
34Tailwind CSS
35Backend
Trial10
4Claude Design
5Dovetail
8Jira
11Airflow
25QGIS
27Google Looker Studio
28Power BI
36FreshService
37MCP & Agent Tooling
38Ollama
Assess08
9Asana
10GitBook
17Airtable
19Microsoft Power Platform
20Enterprise & Low-Code Platforms
21M&E Platforms
29Elastic
39ServiceNow
Hold04
3Balsamiq
18OpenFN
30ArcGIS
31Tableau