Assumptions become requirements
Unverified ideas enter delivery as fixed facts, making later learning feel like disruption rather than useful evidence.
02 · About Floatger
Working Principles
See the practical principles Floatger uses to frame decisions, collaborate, manage uncertainty, and keep delivery connected to its outcome.
The thinking behind the work
Why this commitment matters in practice.
Working principles are useful only when they influence everyday choices. Floatger uses them to decide what to ask, how much process is appropriate, when to expose work, how to discuss trade-offs, and what a responsible handoff requires.
Progress looks busy but unclear
Tasks are moving, but stakeholders cannot connect completed work to product behaviour, decisions, risk, or the intended outcome.
Complexity gains momentum
Patterns, platforms, and abstractions are added because they are familiar or fashionable rather than because the context requires them.
What it means
Turn a stated principle into observable behaviour.
These points describe the intent behind the working model. Their exact expression is adapted to each engagement and its responsibilities.
01
Understand before building
Ask enough about the objective, people, workflow, systems, and constraints to avoid solving the wrong problem efficiently.
02
Make progress visible
Share coherent increments, decisions, questions, and evidence so feedback arrives while it can still shape the work.
03
Choose proportionate structure
Use the process and technology the problem needs, with clear reasons for complexity that must be introduced.
04
Build for continued use
Include maintainability, security, performance, documentation, ownership, and likely change in relevant decisions.
In practice
What the working relationship should make visible.
The form can vary, but useful collaboration leaves context that clients and delivery teams can understand, review, and continue to use.
- 01Questions and assumptions made explicit
- 02Recommendations explained through practical trade-offs
- 03Reviewable increments connected to acceptance
- 04Changes evaluated against priority and outcome
- 05Documentation that supports shared understanding
Shared expectations
Good collaboration needs context from both sides.
These inputs and signals create a practical way to evaluate whether the stated commitment is present in the work.
Context that supports the work
- An honest view of the current situation
- Access to people who understand the workflow and decisions
- Timely feedback and clear decision ownership
- Technical and organisational constraints that affect delivery
What good practice looks like
- The team can explain why important decisions were made
- Working progress can be evaluated by appropriate stakeholders
- New information changes the plan deliberately
- Complexity has a concrete purpose and owner
An honest boundary
Principles guide judgement; they do not make every engagement identical. Activities, documentation, review rhythm, and technical depth should be adapted to the work and its consequences.
How it shows up
A principle carried through the engagement.
Commitments become meaningful through repeatable decisions and behaviours, not only through statements at the beginning.
Clarify before assuming
Identify what is known, believed, constrained, undecided, and explicitly outside the current work.
Choose the next useful step
Shape work around priority, evidence, dependencies, risk, and the smallest coherent progress.
Review real progress
Use working behaviour, designs, decisions, and quality evidence to create focused feedback.
Leave useful context
Record important choices, limitations, ownership, and next actions in a form the intended team can use.
About Floatger
Questions about the approach.
Does a principle-based approach mean there is no process?+
No. It means the process has a reason and is adapted to the objective, uncertainty, risk, team, and decision needs rather than followed mechanically.
How are trade-offs communicated?+
A useful recommendation states the context, relevant options, evaluation criteria, benefits, costs, risks, limitations, and reason for the preferred direction.
How do you respond when priorities change?+
The new information is assessed against the outcome, current work, dependencies, quality, effort, and timing before the scope or sequence changes.
What makes progress reviewable?+
Stakeholders need a coherent piece of behaviour, a design or decision with clear questions, or quality evidence tied to agreed expectations - not only a task status.
Start a conversation
Looking for a clear, collaborative software partner?
Tell us about the product, the current situation, and the decision you need to move. We will help identify a practical way to begin.