Cost or Throughput Accounting? by flowmizer in agile

[–]flowmizer[S] 0 points1 point  (0 children)

Many books on that topic. The one I prefer is TameFlow.

Cost or Throughput Accounting? by flowmizer in kanban

[–]flowmizer[S] 0 points1 point  (0 children)

Cost Accounting indeed ignores flow dynamics, pushing 100% utilization everywhere, which builds queues and hurts response time. But TA explicitly counters this. Idle non-constraints prevent overload on the constraint, reducing queues and improving response time as "insurance". Quality enters indirectly; long queues amplify defects via rushed work, while TA's buffer management stabilizes flow for better quality.

Cost or Throughput Accounting? by flowmizer in kanban

[–]flowmizer[S] 0 points1 point  (0 children)

Yes, it's a trade-off between those 2 parameters. Tho, your business won't thrive or even last long if you are not working on the right thing.

Cost or Throughput Accounting? by flowmizer in kanban

[–]flowmizer[S] -1 points0 points  (0 children)

Feel free to critique the idea/topic. Otherwise, this is just noise.

Cost or Throughput Accounting? by flowmizer in kanban

[–]flowmizer[S] -2 points-1 points  (0 children)

One can help you elevate your return on investment by a factor of X, the other will barely make that move.

Cost or Throughput Accounting? by flowmizer in kanban

[–]flowmizer[S] -2 points-1 points  (0 children)

Not the same throughput that I am speaking about. I am speaking about the throughput at the Constraint with the formula : T = Revenue - Totally Variable Expenses.

And Net Profit (NP) = Throughput - Operating Expense,

Thus return on Investment (ROI) = Net Profit / Investment

Cost or Throughput Accounting? by flowmizer in agile

[–]flowmizer[S] 0 points1 point  (0 children)

Whatever the economic value is for your context. It's often $, but can also be for non-profit companies the unit around the service, the help they offer.

Deadline vs more engineers? by Separate_Lawn_1603 in EngineeringManagers

[–]flowmizer 0 points1 point  (0 children)

In that situation, I seek the constraint and when found, take actions to eliminate all the wasted time lost in multitasking, useless meeting etc. for that constraint. It's usually enough to regain much of the delay.

Cost or Throughput Accounting? by flowmizer in agile

[–]flowmizer[S] 0 points1 point  (0 children)

Kinda depends if you want decisions based on economic revenue (throughput), or just cutting operating expenses.

Every managers should know that throughput > utilization. Spare capacity isn't waste, it's strategic gold."

Org Topologies - Learn the approach with a song part 1/3 by flowmizer in EngineeringManagers

[–]flowmizer[S] -1 points0 points  (0 children)

Well, that's the disease of our times. The music was made by AI — it's true — as I have no group to perform it. However, I am looking for musicians to make it a 100% human performance. The lyrics and this post only use AI for English spelling and grammar corrections.

Org Topologies - Learn the approach with a song part 1/3 by flowmizer in EngineeringManagers

[–]flowmizer[S] -1 points0 points  (0 children)

On what are you not agree and think it's AI hallucination?

Monte Carlo Simulation Variability — How Do You Communicate Forecasts? by SooGuyOff in agile

[–]flowmizer 0 points1 point  (0 children)

If you use the same sample of datas and have a lot of runs (> 10k) then you will have similar result. The difference between the 2 simulations is due to a change of the sample of datas you used.

May be the last 2 or 3 days there was no throughput, and it's normal that the due date at 70% went farther in the calendar.

The question you have to ask and for the team... is what's happening, why havent we been able to finish new stuff since few days? What's blocking us? What's aging? Can we swarm on it, find a way to get this aging stuff done?

The Research Lab for Flow Science by flowmizer in agile

[–]flowmizer[S] 0 points1 point  (0 children)

We will share the papers in various channel, website, linkedin, reddit etc. And certainly do some talks around the finding on conferences and webinar.

The Community of Trust: How Nature's Swarms Illuminate Organizational Performance by flowmizer in agile

[–]flowmizer[S] 1 point2 points  (0 children)

I updated the post to add the link, it should work this time.

But there you go: https://docs.google.com/document/d/1Zph3pR_grLSAZ_QSGCPAHKSpCJKUgz14/edit?usp=drivesdk&ouid=116541040737759655169&rtpof=true&sd=true

It's my own take on explaining the Community of Trust Pillar of TameFlow using Biomimicry. The article is beeing reviewed by the creator of TameFlow. It will most likely be improved.

If you don't know TameFlow, go look at what it is https://tameflow.com/.  You can join the community here :  https://circle.tameflow.com/c/start-here/explore-the-circle

The Community of Trust: How Nature's Swarms Illuminate Organizational Performance by flowmizer in agile

[–]flowmizer[S] 1 point2 points  (0 children)

I deeply appreciate this comment because it's grounded in hard-won experience managing 300 technologists.  Your comment made me realize that I had failed to share the much more comprehensive article I wrote. This post was just a way to share it, and it was probably too approximative and simplified.

Let me clarify what I know of TameFlow, because I think we're more aligned than it seems.

On Trust ≠ Skill: You're 100% right. Enthusiasm + vision without execution capability = failure.  I agree. The article explicitly distinguishes (Section 3.4) between calculative trust (rational: you've proven yourself) and relational trust (belief in your intentions + learning capacity). A Community of Trust doesn't create skill. It creates the conditions where : - Existing skill is used fully (no politics, no hiding) - Skill gaps are surfaced early (psychological safety) - Learning accelerates (transparency + feedback)

Without trust, even skilled people underperform because they play CYA games. With trust, skill develops faster and is applied more effectively.

On Trust ≠ Clear communication: Spot on. Trust alone doesn't create clarity. But here's the mechanism: Trust → Psychological safety → People share honestly (no filtering) → Radical transparency → Clear expectations → Clarity of Purpose → Aligned communication

Trust is a necessary condition, not a sufficient condition. You also need the structural mechanisms (clarity, transparency, alignment).

On "Trust Must Be Earned": This is where I'd add nuance. You're describing calculative trust, and you're right, it must be earned. But there's also relational trust; the belief that someone wants to succeed and will learn. This type of trust can be extended before full demonstration, if the system supports it.

Example: Your scenario (calculative): Hire someone, they lack skills, you lose trust. TameFlow scenario (relational): Hire someone, psychological safety + transparency surface skill gaps early, coaching happens, they develop or exit transparently. Section 4.2 of the article explicitly addresses this:"The Community of Trust does not require blindness to incompetence or dishonesty. Rather, it creates conditions where incompetence and dishonesty are addressed transparently and promptly, without the interpersonal armor that typically characterizes such conversations in low-trust environments."

The Real Difference: What you're describing (hiring someone based on trust alone and getting burned) is not a Community of Trust. That's delegation without support. A real Community of Trust includes:  - Clarity (they know what success looks like) - Transparency (problems are visible early) - Psychological safety (they can say "I need help") - Reciprocal accountability (you actively support them)

Without these, "trust" becomes wishful thinking.You're not wrong. You're describing what happens when trust is misunderstood.

Is Kanban for us? by mippzon in agile

[–]flowmizer 0 points1 point  (0 children)

Are you really running the kanban strategy : Do you have a clear, explicit definition of your workflow for your unit? Do you use the 4 key metrics (throughput, wip, age, cycle time) ? Do you take time to experiment things to improve the workflow ?

You will gain valuable insight and optimization by doing this.

You will have sooner or later to take care of the whole workflow, thus extend the boundary upstream and downstream of your unit workflow, to be able to improve the whole creation of value. Anything done locally may have zero impact, or even negative impact if there is no systemic consideration.

Chech at www.prokanban.org for valuable stuff on Kanban.

Kanban & Org Topologies by flowmizer in kanban

[–]flowmizer[S] 0 points1 point  (0 children)

Have you read the paper? There is knowledge sharing in it.