Simple improvements to making decisions in teams | Object Partners
Summary
Functional requirements, non-functional requirements, user experience, API contracts, tech stack, architecture, database schemas, cloud providers, deployment strategy, test strategy, security, and the list goes on. These are simple and pragmatic tips to improve our existing processes on technical teams. It can be as simple as an email, but consider tools like OpenAPI docs, internal wikis, UML diagrams, and issue/project trackers so that the decision making process weaves into the project’s documentation. Seymour Cray, the seminal pioneer in supercomputing, believed in working in small groups with a single decision maker. Imagine trying to choose a database when we don’t understand the consistency and availability needs (CAP theorem) of our system.