From Assumption to Data-Driven Execution Last week, we redesigned a critical feature and, while doing so, we identified significant problems in the production design. After a follow-up meeting with my manager for further evaluation, I started working on the designs. This time, however, I approached it differently: instead of evaluating assumptions, I used user data as evidence to drive progress. The feature is a timer that users can quickly start anywhere in the app, even without associating it with a specific task. However, there was a constraint: the user could only stop or save the timer after adding the task. Otherwise, they could only pause it - they weren't able to cancel it. The problem we addressed was: how can we let the user stop the timer if they started it accidentally? The simple solution is to add a cancel button beside the start button, but there are other factors to consider: What if the timer runs beyond 15 to 30 minutes? If a user accidentally cancels a timer, how can they recover that tracked time? The simple answer for accidental cancellation is that one confirmation message works well. But what if they cancel the timer within 5–10 seconds of starting it? Does asking for confirmation work then? Probably not. By addressing this, we proposed "threshold management" for cancelling active timers. Now, we have two thresholds: one for within 15 minutes and another for over 15 minutes. The question then became: how do we set the threshold at 15 minutes without knowing the user requirements or having data about their activities? Without data, it’s just assumptions, right? This is where I approached things differently. Since our product's target audience for this timer feature is primarily marketing and sales agencies, I researched their workflows and found their minimum billable increment is 15 minutes. I set this as our standard threshold for the cancel interval. If my manager asks, "How do you know 15 minutes is enough for the user?" OLD ME: I would have simply starred at them or stretched my mind for random thoughts to fill the gap. NEW ME: I can now confidently show the research insights and explain that these are the actual user requirements we are proposing. The Old Way: Moving forward with assumptions and "gut feelings." By the end, it’s purely luck whether the feature is helpful or not. The New Way (or rather, the right way): Moving forward with confidence and evidence. No more relying on luck. I’m aiming to be a problem solver, not just a pixel pusher.

I wondered, I was spending a lot of time on the desk - assuming I was making progress. But in reality - I’m consuming instead of progressing. Spending 9 to 10 hours straight on the table is not actually progress. Focusing 4 to 5 hours is enough to close most of the to-dos of the day. Same mistake, I’m repeating it to this day. What changed? That’s your question right now. Focused work - no distractions. Just work. In this case, you are about to save a lot of time and reduce the stress that occurs when switching between tasks. Focusing on one thing at a time is important. Making realistic to-dos - it seems like 3 to 5 is good for your mental space to accelerate your outcome. If you plan for 10 to 20, you will always procrastinate and not make progress. Never allow entertainment during your work hours, because one constant switch is enough to take you out of focus for longer than you think. Try to work alone with your mind - no music, no entertainment, etc. It feels strange at first, but later, you will see the potential. Time management - Don't assume you have unlimited hours. Treat your time as a scarce resource to accelerate your work and prioritize effectively. These are the lessons I have learned from my own failures. I hope they prove helpful to others as well.

Last week, I worked on a graphic related project. Actually, I'm working as a SaaS product designer. I love to do problem solving, research and especially studying human behavioral sciences (psychology). Bitter point - hate to do graphic related tasks like designing campaign posters. I'm working now in the startup - proudly on the designation of founding designer. I need to withstand every aspect of the situation - in case there is any need for designs and visuals. I casually worked on the visuals - just by presenting the body at the desk, eventually on figma. My mind is in another universe, listening to something unrelated to the work - I did at that time. What I think while designing social media posters - right that time, just polishing the UI ( It will attract the leads). But the assumption is false. And the outcome is also bad - looks good on visuals without the actual meaning - we're trying to tell the audiences. Later, some thoughts clicked - I see the work in many aspects rather than just solely focusing on the visual part. The process is crazy and interesting - explored more about human behavior on perceiving ads, Trust invoking and behavior shift etc.., Once, I spent around hours on iteration just for a single poster. Now, It rarely takes one or two iterations. I shared the outcome with my manager - he liked it at the first sight and approved. Even frustration and stress decreases because of less iterations. Later, My manager told me - one harsh truth, think like a user, validate your work as like an audience. Analyzed - It delivers the value for the right audiences. I wasn't able to describe the feeling - Once I struggled a lot, now it seems like an easy task. Mindset shift happened from “Not just concentrating on the visuals” to “Think in every perspective of the situation, every possible user going through.” My observation: Polished visuals / UI only attracts the user, at the end - just traffic or views. No leads turning into the revenue stream. But meaning and value driven design - uplift both attraction and lead conversion. And in the end - It impacts the revenue. Even get referrals too because of the trust evoked by your design. And always do the work by both mentally and physically enjoyable, liked and peacefully. It automatically drives towards the best outcomes you ever produced. Every problem is created by us - solely all of our problems are created by our own roots. We are always the mother of the problems we have now, before or maybe tomorrow. But the craziest thing, All the problems had the best ever possible solutions lies in our own self. We are creators and also are problem solvers. In between we suffer a lot without even knowing the treasure’s key hidden beyond our own brain. Simple, If you like the work so much, Cortisol is on level - work seems easier than ever. If you keep on stressed with your own thoughts - Cortisol rises, organs stressed. Your mind and body sucks. A simple task seems more difficult to achieve.

—

—

I'm stuck on building my first ever, framer template.

Yesterday, I worked on feature design. Suddenly, while on designing - I figured out one thing - More important aspect in the progress. Even, I'm wondering - How I missed that think, while processing wireframe. Actually, It's a feature for project admins to manage project members working tasks in one single place. Instead of scrolling or switching between project to projects. Instead while with the help of this feature - they can able to go through all at once. In this feature - sub section called 'TASKS WITHOUT DUEDATE'. Here, they can also get the info about the tasks without having due dates. But, what I made a mistake - Not provided options for project admin to update the deadline by using inline date pickers corresponding to their tasks. I simply, Put the visual and flows, just for getting the info for the project admins. What, I realized later - If I not give access for project admins to set due date for the tasks. The project admin needs to ping individually everyone every single time - just only for updating the due date. Even, it gonna be more frustrating - if the quantity of the task persists high. Simple solution, Even in permission level architecture - the project admin is able to edit the task - even they didn't presented in the task as owner. So, letting the project admin to allow set the due date is more effective and minimizes the overhead for the project managers. What I learned - Every single redundant actions can make a huge impact in the system. Doesn't matter - how small it looks or acts accordingly to the system.

I changed my mind about Focus & Productivity because After discovering an outdated yet incredibly underrated method for forcing the brain to engage with deep work, regardless of the distractions or circumstances.

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.

Perfection is a lie - when designing things as a SaaS product designer.I learned through this the hardest way - I'm always looking for the end result, it should be more perfect & trying to decrease the iteration. But in reality, it turns more chaotic than before. Instead of focusing on progression, I kept on thinking and got stuck in the same loop of thoughts, without even starting the work. At this time, mentally I'm exhausted with doubts, fear & some other obstacles. But, if I do the work and make the progression, the doubts, fear & obstacles will be gone - Because my mind believes I'm going to do this more effectively, just by trying and doing the task. Already, I see the results coming up.And, if you do the tasks progressively, there is a high chance of ending with so many effective solutions.Planning is important before starting the work, but more planning & constant thinking will mess up your productivity at some point.5% progression is 5 times more than 0% (Just your thoughts) - just start the work, and the better way will happen by itself by the universe. Trust the process.DO THE WORK, PERFECTION WILL FOLLOW AUTOMATICALLY!

I learned why small annotations and micro-interactions are so important when presenting designs to stakeholders and founders. from What I’ve learned from my failures.

—

—

—

—