TAG-Sprint-BAU Principle

Think of the best identity you are, not the outcomes please. Just the identity, because outcomes rarely breeds a new identity but is definitely a by product of choices and actions typical of that identity.

Now to live that identity, there are few projects that need to be undertaken. Not every project should attract our attention- choose the ones that has highest probability of being around for a very long period of time (ideally should out live us), adding value to our ecosystem; basically one with longest tail compounding.

Now choose the project, and start defining actions that goes into forming practical understanding, application, and real world feedback systems. If we shy away from real life applications and testing our idea- else just keep hoping :D. Make these actions repetitive, just that without thinking about the rigorousness.

This forms the TAG principle that stands for Touch And Go!

That’s it!

TAG-ing essentially makes the action a default piece of your identity through deliberate repetition. Next during the course of any week or month, say we are able to find chunks of time and enough motivation to steer ahead- this forms the basis of Sprint. Sprint requires us to be alert and agile, focus on actions for longer periods of time in a day, and in the process make sure we don’t over burden ourselves with expectations. Okay, as long as the compass is right, speed shouldn’t be a worry- but why not take advantage of that motivation/inspiration spike?! Moti and inspi are like the battery cells, these die off as well, so catch hold when around.

This is all about cementing a foundation fast enough to keep things interesting by way of being an absolute opportunist!

Finally the third stage, BAU or, Business As Usual. Those actions through deliberate repetitions, sprints, finally with time matures and our ability to sustain it no longer needs planning. Gosh! this is one holy status that I wish to pin my long term projects into :-)

Now, carefully put together, this is your Kanban in action. But, a huge difference is we are not tagging actions against quick, short-lived statuses like to-do, in progress, testing, done, Nope! This is our identity, requires a simple but mature framework that’s purely defined by processes not by mere state of action. Just these three TAG-Sprint-BAU, and few role defining long term projects that’s it. Less edits, just three categories based to build processes, and a handful of long term projects.

Better to not drool over short term projects, else we can’t use the power of compounding. Yes, we can have milestones within a project, that should be carefully crafted to promote just enough charge to keep us moving in the right direction.