Skip to content

Swap sections 'Decide with Data' and 'Build in the Open' #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
timmcconville wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Swap sections 'Decide with Data' and 'Build in the Open' #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions core-tenets/collaboration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,14 @@
Our role isn't just to build what's requested, but to proactively engage with stakeholders as strategic partners. By understanding their goals and challenges deeply, we can co-create the best solutions.


## Decide with Data
## Build in the Open

Our planning and decisions should be guided by data and evidence, not just intuition. Whether it's analyzing user behavior to justify customization, calculating the cost of software development, or measuring the impact of our work, data is our common language. This approach makes our choices objective and focuses our efforts on what delivers the most value.
We should operate with full transparency to our business partners. This means clearly communicating the 'why' behind our decisions, the trade-offs we're making (e.g., speed vs. cost), and the progress of our work. When we explain ‘why’, we build trust and ensure everyone understands the long-term vision we're working toward together.


## Build in the Open
## Decide with Data

We should operate with full transparency to our business partners. This means clearly communicating the 'why' behind our decisions, the trade-offs we're making (e.g., speed vs. cost), and the progress of our work. When we explain ‘why’, we build trust and ensure everyone understands the long-term vision we're working toward together.
Our planning and decisions should be guided by data and evidence, not just intuition. Whether it's analyzing user behavior to justify customization, calculating the cost of software development, or measuring the impact of our work, data is our common language. This approach makes our choices objective and focuses our efforts on what delivers the most value.


## Trust but Verify
Expand Down