Tools#
Tools that support the SDLC outside of code itself: planning, tracking, designing, communicating, and accumulating institutional knowledge.
Issue Tracking and Project Management#
The tools where work gets tracked. The choice mostly comes down to weight class; enterprise teams default to Jira, product teams in the 2020s default to Linear; open-source projects stick close to the source with GitHub or GitLab issues.
Jira, the enterprise default; deeply customizable; heavy when over-customized.
Linear, modern, opinionated, fast; popular with product teams in the 2020s.
GitHub Issues + GitHub Projects, close to source; sufficient for many open-source and small teams.
GitLab Issues + Boards.
Shortcut (formerly Clubhouse), mid-weight.
Asana, Monday.com, generic project work.
Trello, simple Kanban.
YouTrack, JetBrains.
The tool matters less than the discipline; the discipline matters less than the team’s understanding of why they’re tracking what they track.
Documentation and Knowledge Bases#
Where institutional knowledge lives. The split is roughly “managed SaaS” (Confluence, Notion, Coda) vs “in-repo Markdown + static-site generator”; both work, the trick is having one standard place rather than a Wiki, a Notion, a README, and a Slack channel that all disagree.
Confluence, the Jira companion; ubiquitous in enterprise.
Notion, modern, lightweight, popular for knowledge bases and lightweight project tracking.
Coda, docs / databases hybrid.
Slab, focused on engineering wikis.
In-repo Markdown, often the best place for docs that change with the code.
MkDocs, Docusaurus, Sphinx, Antora, doc site generators.
The most-read docs are usually the ones nearest the code.
Design and Whiteboarding#
The visual side of design and collaboration. Figma is the dominant UI tool; Excalidraw and tldraw cover the quick-whiteboard niche; Mermaid and similar text-based diagrams keep diagrams close to the code that documents them.
Figma, the dominant UI design and prototyping tool.
Sketch, macOS-only; Figma’s predecessor in popularity.
Adobe XD, declining.
Penpot, open-source Figma alternative.
Excalidraw, sketchy diagrams; great for RFCs and casual whiteboarding.
tldraw, collaborative whiteboard.
Lucidchart, draw.io / diagrams.net, structured diagrams.
Mermaid, text-defined diagrams; renders in GitHub / GitLab Markdown.
Communication#
The chat and async-doc tools that mediate most team coordination. Slack and Teams dominate; the better question than “which tool” is “what gets written down”. Async-first written cultures outperform meeting-only cultures, especially at distance.
Slack, the default work chat.
Microsoft Teams, in Microsoft-aligned organizations.
Discord, common in open-source and gaming communities.
Zulip, threaded; underused; excellent for async-heavy teams.
Matrix / Mattermost, self-hosted alternatives.
Email, still the durable record for many decisions.
Async-first, written status updates and decision docs beat meeting-only cultures, especially for distributed teams.
Meetings and Calendaring#
The tools for synchronous time. Async beats sync for decision documentation; sync beats async for relationship building and ambiguous topics. The right defaults make the right choice easier.
Google Meet, Zoom, Microsoft Teams, video meetings.
Calendly, Cal.com, Savvycal, scheduling without back-and-forth.
Async > sync for most decision documentation; sync > async for relationship building and ambiguous topics.
Surveys and Feedback#
The tooling for measuring how the team and the product are doing. Generic surveys for one-off questions, engagement platforms for ongoing pulse checks, async-standup tools for the “what did you do today” rhythm without a synchronous meeting.
Typeform, Google Forms, general purpose.
Officevibe, Culture Amp, Lattice, engagement / performance.
Customer Support and Feedback#
The user-facing side of feedback. Support inboxes and engineering-flavored helpdesks for one-on-one issues; feature-request boards for crowdsourced prioritization; product analytics for measuring what users actually do (vs. what they say).
Intercom, Zendesk, Help Scout, support inbox.
Productboard, Canny, feature feedback.
Time Management#
The non-tooling side of getting work done. The right tools matter, but the right defaults matter more; defended calendars, async-first responses, written working agreements that are actually agreed.
Calendar, defended deep work blocks; meeting-free days when feasible.
Working agreements, shared expectations on response times, meeting attendance, on-call.
Async-first defaults, if a question can be answered in writing, start there.
The right tools matter, but the right defaults matter more.
Composition#
There’s no standard SDLC stack; common modern combinations cluster around team size and culture. Pick the smallest set that lets the team focus on the work; every additional tool is more places knowledge can fragment.
Lean engineering team: Linear + Notion + GitHub + Slack + Figma + PostHog.
Enterprise: Jira + Confluence + Bitbucket + Teams + Adobe XD + Tableau.
Open source: GitHub Issues + Discussions + Discord / Matrix + the source itself.
Pick the smallest set that lets the team focus on the work.