Start by getting the whole team together for one week to write the mission statement. Then audit every backlog item against it and remove anything that does not directly advance it. Set the new sprint planning capacity at the actual average from the past four sprints minus ten percent.

#Lean #Agile #MissionDriven #SustainablePace #SmallTeam #Manufacturing #BurnoutPrevention #ContinuousImprovement #StartupLife #TeamHealth (22/22)

Start with your next demo. Add a thirty-minute hands-on session where stakeholders use the features themselves. Prepare role cards for three stakeholder perspectives. Set up a shared digital board with Works Well, Needs Change, and New Ideas columns. Have the facilitator populate it in real time as stakeholders react.

#Agile #SprintDemo #Lean #HealthcareSaaS #StakeholderEngagement #BuildMeasureLearn #ProductManagement #FeedbackLoop #TeamCollaboration #Matsushita (20/20)

The past two months, I helped coordinate the "Phase Transitions..." research semester programme at CWI (https://www.cwi.nl/en/events/research-semester-programmes/phasecap-phase-transitions-in-combinatorics-algorithms-probability/). It ended last Friday, and still I feel "hungover" from the intensive blur of activities/developments/ideas. Very grateful to my team --Feri, Jop, Serte, Carla, Noela, Guus-- we did it!

In parallel, during the same two months, after the dawn of recognition of what has arrived (after a tip from Jeroen), I underwent a kind of phase transition myself. Avowed refusenik in March (see https://mathstodon.xyz/@kangmeister/115252549665766971); an "anti-Gemini" research working group in April; compulsive button-pressing in May. (And yes, I *know* it is easy to set it up for pressing fewer buttons...)

That poetic part of me (or whatever remains of it) is allured by the term, "cognitive surrender", if only to help in my search for the right words to describe the sharp changes underway in various facets of mathematical life/growth.

#CWI #combinatorics #algorithms #probability #conferences #generativeAI #formalization #lean #scientificpublishing

PhaseCAP: Phase Transitions in Combinatorics, Algorithms, Probability

Combinatorics, Algorithms, Probability

Start by defining the client impact for your next three experiments, creating a risk budget for your top five clients, and scheduling a monthly one hour client risk review that includes your engineering leads, client success managers, and leadership team.

#RiskManagement #Lean #DevOps #SocialResponsibility #EngineeringLeadership #ContinuousDeployment #CanaryTesting #ClientSuccess #BuildMeasureLearn #TechServices (34/34)

I'm trying out Aristotle and Lean Copilot for formalizing and proving theorems, and, so far, Aristotle feels way more powerful. Lean Copilot's suggestions aren't always right. Aristotle, on the other hand, can bring in previous lemmas, figure out missing hypotheses, and so on –besides, of course, finishing the proofs themselves.

Disclaimer: this is probably mostly down to the underlying model: Aristotle uses a specialized in-house model (within an agentic architecture), while Lean Copilot is using a more general-purpose one (and not a particularly strong one, at least in my setup... DeepSeek-R1, I think).

#lean #theoremproving #aristotle

Start by setting the expectation that every team member will identify at least one improvement opportunity this iteration. Create a board where those opportunities are visible to the entire team.

#ContinuousImprovement #Lean #B2B2C #RetailTech #Agile #TeamCulture #Leadership #ProcessImprovement #Retrospectives #OperationalExcellence (26/26)

Start by identifying the three metrics that most directly reflect whether your team is delivering value to healthcare providers and patients. Write them on your team board. Agree on the thresholds that will trigger action.

#Lean #ToyotaProductionSystem #HealthcareB2B2C #KPIs #Metrics #ProcessImprovement #Agile #GenchiGenbutsu #ContinuousImprovement #SmallTeamLean (27/27)