Good Team vs Bad Team


There is a profound difference between how the very best product companies create technology products, and the rest. And I don’t mean minor differences.  Everything from how the leaders behave, to the level of empowerment of teams, to how the organization thinks about funding, staffing and producing products, down to how product, design and engineering collaborate to discover effective solutions for their customers. Below is a glimpse into some of the important differences between strong product teams and weak teams:

  • Good teams have a compelling product vision that they pursue with a missionary-like passion.  Bad teams are mercenaries.
  • Good teams get their inspiration and product ideas from their scorecard KPI’s, from observing customers struggle, from analyzing the data customers generate from using their product, and from constantly seeking to apply new technology to solve real problems.  Bad teams gather requirements from sales and customers.
  • Good teams understand who each of their key stakeholders are, they understand the constraints that these stakeholders operate in, and they are committed to inventing solutions that work not just for users and customers, but also work within the constraints of the business. Bad teams gather requirements from stakeholders.
  • Good teams are skilled in the many techniques to rapidly try out product ideas to determine which ones are truly worth building.  Bad teams hold meetings to generate prioritized roadmaps.
  • Good teams love to have brainstorming discussions with smart thought-leaders from across the company.  Bad teams get offended when someone outside their team dares to suggest they do something.
  • Good teams have product, design and engineering sit side-by-side, and embrace the give and take between the functionality, the user experience and the enabling technology.  Bad teams sit in their respective functional areas, and ask that others make requests for their services in the form of documents and scheduling meetings.
  • Good teams are constantly trying out new ideas in order to innovate, but doing so in ways that protect the revenue and protect the brand. Bad teams are still waiting for permission to run a test.
  • Good teams insist they have the skill sets on their team necessary to create winning products, such as strong interaction design.  Bad teams don’t even know what interaction designers are.
  • Good teams ensure that their engineers have time to try out the discovery prototypes every day so that they can contribute their thoughts on how to make the product better.  Bad teams show the prototypes to the engineers during sprint planning so they can estimate.
  • Good teams engage directly with end-users and customers every week, to better understand their customers, and to see the customer’s response to their latest ideas.  Bad teams think they are the customer.
  • Good teams know that many of their favorite ideas won’t end up working for customers, and even the ones that could will need several iterations to get to the point where they provide the desired outcome.  Bad teams just build what’s on the roadmap and are satisfied with meeting dates and ensuring quality.
  • Good teams understand the need for speed and how rapid iteration is the key to innovation, and they understand this speed comes from the right techniques and not forced labor.  Bad teams complain they are slow because their colleagues are not working hard enough.
  • Good teams make high-integrity commitments after they’ve evaluated the request and ensured they have a viable solution that will actually work for the customer and the business.  Bad teams complain about being a sales-driven company.
  • Good teams instrument their work so that they can immediately understand how their product is being used and make adjustments based on the data.  Bad teams consider analytics and reporting a “nice to have.”
  • Good teams integrate and release continuously, knowing that a constant stream of smaller releases provides a much more stable solution for their customers.  Bad teams test manually at the end of a painful integration phase and then release everything at once.
  • Good teams obsess over their reference customers.  Bad teams obsess over competitors.
  • Good teams celebrate when they achieve a significant impact to the business KPI’s.  Bad teams celebrate when they finally release something.

Great Virtue


What does being honest mean? Being honest means to tell the truth even when you have opportunities to lie. Being honest means doing the honest thing even when no one sees. Being honest means being truthful to one self and others at all times, no matter what.

What does being kind mean? Being kind means doing something for other people, even the people don’t know well. Being kind means helping others without hoping for anything in return. Being kind means making the world a better place for others.

What does being loyal mean? Being loyal means being there for someone no matter how hard it is. Being loyal means being committed to the promises that you have made before. Being loyal means never to let someone down even in the darkest hour.

What does being persistent mean? Being persistent is keep on trying even when the last attempt didn’t succeed. Being persistent is striving to achieve your dream against all odds.

What does being patient mean? It means you are willing to wait for something good, and don’t expect instant results. It means that you realize that everything has its own time. It means that you understand that it takes time to achieve something extraordinary.

What does being smart mean? It means you always think ahead and be prepared. It means that you observe your surrounding to collect as much information as possible and use them accordingly. It means knowing what to do in any circumstances.

What being diligent mean? Being diligent means working harder and giving more than expected. Being diligent means doing what you have to do and more without being told. Being diligent means practicing self-control and giving time and energy to do more for other people.

What does being proactive mean? Being proactive means thinking ahead and doing something before it’s too late. Being proactive means controlling the situation instead of being controlled by it. Being proactive means thinking of ways to make better without being asked.

What does being open minded mean? It means that you are willing to try new things. It means that you understand that everyone is possible (even when they seem impossible). It means that you appreciate and willing to embrace differences.

What does being grateful mean? It means being thankful for your condition whatever they are. It means knowing that God will provide what you need and not what you want. It means realizing that there are many who are less fortunate that you are.

*note to my self*



Orang miskin juga manusia, mereka juga harus dimanusiakan. Sehingga yang dimanusiakan jangan hanya orang kaya, pejabat, ternama saja karena mereka memiliki modal.

#renungan #pengingatdiri #jangansombong


Awali dengan basmalah, menyapa dan memasuki tempat dengan ucapkan As-salamu’alaykum, isi waktu luang dengan istighfar, dan menenangkan hati dengan baca Al Qur’an, kaya dengan bersedekah, belajar dengan dipahami.

*note to my self.



diajarin tentang teori menjadi manusia bermanfaat pertama kali sewaktu kuliah dulu (liqo).

Makasih kaka mentor 🙂



The key is in the heart belongs to Allah SWT.

If our heart is right, then: attitude, expression, words, behaviour, body & soul…

Insyaallah those are also right, even in the world and life after.




Semakin sering membaca Al Qur’an, semakin sering memahami tafsir dari ayat demi ayat Al Qur’an, semakin hanya bisa menangis & merasa kita manusia yang tak berdaya…

Yaaallah, maafin aku…

‘Astaghfirullahal’adzim, alladzi la ilaha illa huwal hayyul qoyyumu wa atubu ilaih’