Priority: People, Process, Product and Profit

Taggun is a bootstrapped company. We don’t need funding from investors, so we have the freedom to set priorities for ourselves. Here are my thoughts about Priority: People, Process, Product and Profit, in that order.


A good person (member) helps team members to get better at work. A bad member just complains. A good member accepts the quirks of his/her weirdo team members. A bad member wants everyone to act the same way. A good member is genuine and seeks the trust of the team. A bad member says shit they don’t mean. A good member is courteous and honest when giving feedback. A bad member would say things to avoid conflict. A good member learns to understand team members’ point of view before speaking. A bad member speaks without understanding team members’ point of view. A good member commits to the decision made by the team even if they disagree with it. A bad member just sits and waits for the moment to say, “I told you so”. A good member makes emotional investment at work. A bad member thinks they don’t get paid enough to be emotional at work. A good member makes his/her work environment a comfortable place to work in, even if it is only for a selfish reason. A bad member turns his/her work environment into a smartness competition to one-up team members.


A good process is defined at the company level and fine-tuned for each functioning team. A bad process is defined at company level and expects everyone to follow the process to the tee. A good process focuses on routines and system. A bad process focuses on targets and goals. A good process starts with why. A bad process starts with how. A good process develops organically over long period of time. A bad process is static and refuses to adapt to change. A good process allows room for errors. A bad process leaves no room for errors. A good process takes advantage of available resources and tools to be effective. A bad process requests for more budgets and resources to be effective. A good process is measured and the result is then reviewed internally by the team to improve. A bad process is measured and the result is then published externally for vanity purposes.


A good product is simple and easy to use. A bad product looks beautiful but it is not intuitive to typical users. A good product hides the advanced features and complexity from the first screen. A bad product dumps every option and information available on the screen. A good product will have limitations; the limitations with workarounds are communicated to the users. A bad product tries to tackle everything. A good product gains momentum from the conception of idea, development and launch on the market. A bad product gets bogged down by details before the development starts. A good product gets better after it is used in production by real users. A bad product tries to be the best before it reaches to production. Developers know it is a good product when it is easy to extend and maintain. A bad product takes developers a long time to add simple features and maintain the software. A good product gets pruned every year. A bad product grows and grows every year.


A good profit is made by doing more creating than selling. A bad profit is made by doing more selling than creating. A good profit is made by making things simple for the customers. A bad profit is made by complicating things and creating confusion for the customers. A good profit is sustainable and it grows every year. A bad profit is like a one-time-get-rich-quick scheme. A good profit comes with risk; calculated risk. A bad profit is guaranteed. If profit is guaranteed with zero risk, there will be easy competition in the market. Guaranteed profit will not last long. A good profit is generated by reinvesting the profit to the people, process and product. A bad profit is generated by squeezing money out of the people, process and product.