—

—

Figuring product flow before touching UI designs because If I do not do this, Eventually I ended up in a difficult situation (confusion in between flows) and not have the complete overview to estimate the proper execution time. Uncertainty leads to frustration and procrastination. Even I'm moving in a blinded direction hoping for better outcome. But ended up in dungeon.Planning & making the architecture before UI execution is so crucial to avoid misunderstanding and reworks in between you & your manager or CEO.

Discipline over Excuses because It's hard to maintain, but more effective to live the life, you wished for the way, you want!

I learned one more valuable things from my mentor & my boss and also my well wisher - He always told me - Before touching figma, understand the problem context and then suggest me to work on UI part next. The exact mistake, I repeated a lot because of deadlines and being in some complex situations. Unfortunately, in the end - the mistake addressed sharply by my boss. Today, I realized and corrected my mistake, work for the value & the impact I create - not for the submission or working like you don't like the work.

Arul, as of now, we're sharing business-related book knowledge with our target audience. Am I right? If I'm wrong, correct me.

—

—

This hackathon - taught me some many valuable things for my career.1. Data (evidence) backends great and clear decision on the problem.2. Assumptions cost more than, what we think about it.3. Handling with different set of persona's and Geographic's of the users.4. Practicing with behavior changes of the users.Main point - Assumptions, for example - we believe this upcoming feature will gonna help the user a lot, but in reality - definitely, it's not, just like a normal feature exist. Why it happens - basically it because of lack of research and analyze of the requirement of the users. By the end - a lot of time resources & more human forces wasted for what the user actually, don't want as of now in their need's. The magic for retention of the user is simply - just fulfilling their needs in simple ways. No overwhelming steps - easy & less mental effort work. If they find it your product, simplifying & solve their needs; that all the user gonna retented for sure.Solve their problems, automatically they follow - even if it's paid or requires money.

Why is critical thinking more important? Learnings from hackathon.My mentor & my boss always told me to understand the customers while designing any feature or UI designs. Because customers are the real bosses of our business. Without them, our product is just presents, not converts. In today's modern world, people are only stick with it if the product solves their needs & problems. Otherwise, they ignore it badly.I always keep this in my mind while designing, but after attending the hackathon's initial session. I realised the truth potential & demand of critical thinking before execution. It shapes the entire path.Huge shout out to RK & Arul for providing opportunities like this.

Another thing - critique & feedbacks for the my designs. When ever, I explaining the designs with the developer team, I will face a lot of good questions & points, I missed out. I learned this - Collaborating with founders & dev folks - would open a door for more clarity on the process. Improves the quality of the outcome. Importantly, the burnout decreases. Expectations matched perfectly.

Learned this today with help of my mentor - When every, I design for users, I only considered the user requirements, persona's & behavior's. Additionally, consider developer handoff. But, in some cases, I missed to think like a PM. I constantly rushing for the outcome and deadline. Not on the quality of the outcome. Today, I paused a bit and thinks slowly. Then, I realized my mistakes, I made. So, I not failure here - I realized & learned my mistakes and make a note, not to repeat once again.