Six months of 18-hour days and the promotion still did not come
Five years into her career, after six months of 18-hour days on a critical project, she walks into her review expecting a promotion and hears: you are not there. Sreeja Nair, a Staff Product Manager at Qualcomm, borrows a framework product teams use to rank features to explain why hard work alone so often goes unrewarded. So which work actually makes managers take notice?
Learn how the Kano model sorts your work into must-haves, performance tasks and delighters
Sreeja Nair, a Staff Product Manager at Qualcomm, argues that hard work alone rarely earns promotion because stakeholders judge the output they see, not the hours invested. She maps the Kano model from product management onto careers, showing how to move from must-have core tasks to "delighter" work that makes you stand out, and shares practical ways to free up time for it.
“Remember, most people do not get promoted for solving their own problems, but people get promoted for solving their managers' problems.”
“Focusing all our time on these tasks makes us cookie cutter.”
What you will learn
Classify your work into core must-haves, performance tasks and delighters using the Kano model.
Judge your output the way your stakeholders see it, not by the hours you put in.
Prioritize ruthlessly with the big rock, small rock framework and time boxing to protect time for high-impact work.
Free up capacity by automating, delegating and mentoring others on core tasks.
Spot strategic gaps beyond your role and step up with proposed solutions to stand out.
Key takeaways from the speaker
Learn product management frameworks to evaluate your personal brand
Exercise strategies to differentiate your personal brand
Develop an understanding of how differentiating your personal brand is similar to how you differentiate the products you build
Details
Level
All levels
Format
Talk
Technical depth
Non-technical
For
Early career, Mid-career
Length
21:41
Published
July 2021
Questions this talk answers
Why doesn't working long hours lead to a promotion?
Stakeholders judge the output they see, not your effort. If all your time goes to core tasks that are expected of you, they will not be dissatisfied, but they will not be more satisfied either.
What is the Kano model?
A product management framework developed by Noriaki Kano that maps how well a feature is delivered against customer satisfaction. It sorts features into must-haves, performance features and delighters.
How does the Kano model apply to a career?
Input becomes the x axis and output the y axis. Core tasks are must-haves (case A), solving your manager's problems is proportional performance (case B), and strategic problems for the wider organization or industry are delighters (case C).
How can you make time for delighter work?
Prioritize ruthlessly with a framework such as big rock, small rock, then time-box tasks or use Pomodoro. Free your calendar by automating, delegating and mentoring others on core tasks.
Does a delighter stay a delighter?
No. Stakeholder expectations change over time, so work that delights at one stage can become core after a promotion, and you need to stay in an eternal beta to keep finding new delighters.
About this talk
Differentiating one's personal brand is key to career growth. Strategizing this personal brand differentiation similar to product differentiation is key to career advancement. In this talk, view your personal brand through a product lens; learn product management frameworks to analyze your personal brand and create invaluable differentiators.
I will use a product management framework to explain how we prioritize, rank and develop features for our products. Using the same framework for our career, I will explain how we can focus on finding our key strengths, develop our USP and ways to grow it as you rise in your career.
Build a vision for your personal brand based on product management principles.
Audience:
This talk provides a framework to anyone aspiring to scale, rise and grow in their careers at all levels. It would particularly be useful for mid-career professionals from all fields who feel stuck in their roles and are looking for steps to scale their personal brand . I will use personal stories from different stages of my career to connect with the audience and share how this framework has helped me accelerate my career, move across continents and pivot from engineering to product management.
Get promoted by solving your manager's problems (48 s)
Delighters: the work that makes you stand out (77 s)
Speaker 1: Okay, everyone. Good morning, good afternoon, and good evening, wherever you are in the world. I am Sreeja Nair, a product management leader at Qualcomm. Now, how many of you here know who Qualcomm is actually or what Qualcomm does? If you know, type it out in the chat window. I'd love to know if you know about Qualcomm.
Speaker 1: There I work early. If you know, I'd love to hear that. Otherwise, let me introduce you. So Qualcomm is the world's leading wireless technology innovator and the driving force behind the development, launch, and expansion of 5G. When we connected the phone to the internet, the mobile revolution was born. Now, coming to my role, I work in the wireless connectivity division at Qualcomm, interacting with wireless enterprise providers to align their needs with Qualcomm's Speaker 1: wireless portfolio. And today, I'm honored to be here and sharing my experiences on how to stand out and build your USP with each one of you. Thank you for joining me today. Please feel free to use the chat window as I've been reiterating. Let us dive right in.
Speaker 1: Now, all of us work really hard to be great at our jobs. In fact, we want to be the best at everything we do. In return, we have expectations. Speaker 1: What we expect is that we will be rewarded with promotions. Or it could be money. Or sometimes it's just an appreciation for our work in public.
Speaker 1: But many a time, or let's say most times, we are disappointed. We're just like most. And just like most, it has happened to me too, really. Speaker 1: I was about five years into my career. And I was working more than 18 hours on a really critical project for the, for the team for almost six plus months.
Speaker 1: And I was quite proud of my work. I confidently went in for my performance review at the end of the project. I expected a promotion. Let me tell you no less. Speaker 1: After all, I had given every, I had given it everything. So what do you think happened? You know, I mean, when I went in and asked for this promotion, or when I went in with this expectation, I got five words.
Speaker 1: You are not there. Or a similar one in your career. Type in the chat window. If you've heard this at any point, and we're not in one room, so that the best I can do is, you know, get you to type into the chat window. Speaker 1: And maybe I can, you know, take a look. Yeah. Thank you for the, thank you for some engagement there.
Speaker 1: Now I'm sure many of us have, and I've acted just like any of us. Did I put in so many hours and sacrifice my life for this? Speaker 1: I was sad. I cried my heart out. And of course I blamed my manager. Speaker 1: Blaming our managers or someone we work with at this point really comes easy.
Speaker 1: But it is strange that when we end up becoming managers, many of us, or rather most of us have to make similar decisions because the trade-offs and the constraints. Speaker 1: Now thinking through my options at this stage, I realized I had two options. One, I could look for a new job or I could look for answers.
Speaker 1: And it was not that I did not have hints all around me. I saw folks who had received promotions in or two promotions in three years. Speaker 1: And then there were others who are working far less than me and still moving ahead and making progress. Speaker 1: The more I searched for answers, the more I saw a pattern.
Speaker 1: It was all about the ratio of output to input. Let me tell you what I mean. Speaker 1: In other words, a lot of people call this as productivity, the ratio of production output to input. Speaker 1: So simply put, there are three possible scenarios where your input is really large. Speaker 1: In this case, as you can see case a, where I is really large and always really small.
Speaker 1: And when I mean, Oh, it is the output in terms of how your stakeholder or your management views your output. Speaker 1: Not what you view it as, but what the world sees of you, what your stakeholders see of you. Speaker 1: And then this case B where your input and output are proportional. Speaker 1: And finally you have case C where I is small and O is really large.
Speaker 1: That is your input is small and O, your output is really large. Speaker 1: Needless to say, my current state was a case A and I was really working hard, but I was not getting anywhere or not getting to where I wanted to be. Speaker 1: But what I wanted to be technically is case C, which is I directly or output greater than input considerably greater than input.
Speaker 1: So in fact, we all want to be case C. We all want our reward to be higher than our investment. Speaker 1: Then why is it that only few of us get there? Speaker 1: Why something that a few of our friends colleagues get so effortlessly seems so elusive to many of us? Speaker 1: So I introspect it, I read articles, you know, I, you know, I was researching this topic, but I found no direct solution.
Speaker 1: And that question kept nagging at me happens to you right when you don't find a solution to something keeps nagging at you, how do I solve this? Speaker 1: But when I joined product management, I started reading books to explore this discipline. Speaker 1: And one day I stumbled upon a framework. Speaker 1: This seemed to be really the answer that I was looking for, at least in my opinion.
Speaker 1: The process from going from case a, case a on the slide to case C on the slide where output is much greater than input where I want it to be. Speaker 1: Now, since childhood, I have loved modeling the complex world around me in simple work, the same works. Speaker 1: Probably that's why I ended up being an engineer.
Speaker 1: And today I'm delighted to share one such framework that helps me maximize my output with the minimal input. Speaker 1: And in turn, stand out and find my USP. Speaker 1: Now, some of you know the framework as the famous Kano model. Speaker 1: The Kano model was developed by Noriyaki Kano, a Japanese researcher. Speaker 1: What this model does, it maps the complexity of developing product features with customer satisfaction.
Speaker 1: If you know about this model, have ever heard about it, use it, please type in the chat window. Speaker 1: And if you like it, do type that as well. Speaker 1: You know, UI and research, UI researchers or UI folks or even designers and product managers have used this framework a lot. Speaker 1: So I'm sure they might be familiar.
Speaker 1: So, but what I'm doing is I'm trying to brief the others so that they quickly come to speed on the model before we go into how it maps out. Speaker 1: Okay. Speaker 1: Now it starts with the goal of building products. That is the goal is customer satisfaction. Right? Speaker 1: So one axis of this is customer satisfaction.
Speaker 1: What you're doing is you're technically plotting X axis and Y axis and trying to map, you know, how features kind of fall in or how they should, how they map along these two dimensions. Speaker 1: So the customer satisfaction dimension or vector ranges from total satisfaction called a delighter to total dissatisfaction, which is called frustration.
Speaker 1: As you can see on this axis, the other part or the X axis, you know, as we see is functionality. Speaker 1: That is how well we have implemented and delivered the feature for a product and what it offers really for the customer. Speaker 1: And these two dimensions together actually form the basis of the Kano model as we knew it.
Speaker 1: And then determine how our customers feel about our product feature. Speaker 1: Let us go, you know, you see these curves. Speaker 1: So let us go into these curves one by one. Speaker 1: Let me quickly explain to you how they map out. Speaker 1: So let us talk about the first curve, the first curve, meaning the red one here.
Speaker 1: Let me get my pointer. Speaker 1: Okay. Speaker 1: So you see the red curve here. Speaker 1: So the core feature, these are must-haves. Speaker 1: These are expected by customers. Speaker 1: If a product doesn't have them, it will be considered incomplete or just plain bad. Speaker 1: Now these kind of features are called must-haves.
Speaker 1: We need to have them, but that does not mean our customers will be more satisfied. Speaker 1: They will just not be dissatisfied. Speaker 1: For example, we expect our phones to be able to make calls. Speaker 1: The car should have brakes. Speaker 1: Having any of these won't make us happy, but lacking them will definitely make us angry or towards a product or a service.
Speaker 1: As you can see from this, from this red curve of, you know, and the lower part of the graph, you know, the way it maps out, you can see that. Speaker 1: In simple words, these are non-negotiables. Speaker 1: These are what you have to deliver in a product, right? Speaker 1: Now coming to this blue line up here.
Speaker 2: Some features have a proportional relation between satisfaction and functionality. Speaker 1: The more we provide, the more satisfied our customers become. Speaker 1: When you're buying a car, it's gas mileage sometimes, or which is a performance attribute, or while buying a laptop, it's your battery life, which is a performance feature. Speaker 1: The more you have each of those, the greater your satisfaction.
Speaker 1: Every increase in functionality leads to increased satisfaction. Speaker 1: As you can see, it's a linear representation. Speaker 1: And finally, it's a third curve, which is unexpected features, which when presented, can cause a positive reaction or surprise the users. Speaker 1: These are called your delighters. Speaker 1: Now think of the first time you controlled the Netflix on your TV using Alexa, or when Shazam app caught the right song in a crowded station.
Speaker 1: You felt wowed. Speaker 1: You really felt delighted, right? Speaker 1: It was not something that you saw before. Speaker 1: Now, in case you do not know what Shazam is, let me tell you, Shazam kind of identifies the music playing around you. Speaker 1: When Shazam was first introduced, it did not catch all the songs.
Speaker 1: In fact, it identified a really low percentage of the songs correctly, and it failed most of the time. Speaker 1: But yet it caught on. Speaker 1: People focused not on the failure, but were amazed at what it delivered. Speaker 1: And that's what delighters are when you start off, you know. Speaker 1: This just delighted the customers.
Speaker 1: Eventually, you have to find new delighters, but that's one example of how people got delighted. Speaker 1: Now in this graph, the Netflix with Alexa or the Shazam app, when first introduced will be on the green curve here. Speaker 1: You know, when you then the customers didn't know they wanted it, but they love what they got.
Speaker 1: And as you can see, the curve throughout the customer, the curve throughout has a higher customer satisfaction level, even with minimal functionality. Speaker 1: Now, when I saw this model as a product manager, I thought how remarkably it represents our career. Speaker 1: Mapping this model to our careers, the X axis will be the input and the Y axis, the output.
Speaker 1: All of us have finite time and energy similar to, you know, how we build our products. Speaker 1: We have finite resources, we have finite investment. Speaker 1: In our case, it's similar, you know, time and energy. Speaker 1: How we use this time and energy to maximize what we deliver is definitive to our success.
Speaker 1: Similar to our products. Speaker 1: Those products are successful that maximize. Speaker 1: And translating these three cases, I explained at the beginning. Speaker 1: Here's how the three graphs for your I/O will look like. Speaker 1: As you can see, case A, where your input is really high. Speaker 1: Now here, however hard you work, the output curve will always stay below the origin.
Speaker 1: If you're here, you're focused on core tasks, which are expected of you. Speaker 1: These are tasks that need to be done. Speaker 1: Now when you, you know, for example, joined as an engineer, fixing bugs was expected of you. Speaker 1: When you joined the marketing team, developing collateral was expected of you. Speaker 1: When you joined sales, closing a client deal is expected of you.
Speaker 1: You've got a path here and there for starting, but then you soon realize you did not stand out. Speaker 1: This is your core. Speaker 1: Focusing all our time on these tasks makes us cookie cutter. Speaker 1: And in most cases, we end up being dissatisfied at not being able to stand out and make an impact.
Speaker 1: As you can see from the Kano model comparison, if you are here, you, most of your output is likely core features. Speaker 1: You need to deliver them, but that will not increase the happiness or satisfaction of your stakeholders. Speaker 1: That's your management, your managers, or your organization. Speaker 1: They just won't be dissatisfied.
Speaker 1: Now look to the second curve. Speaker 1: This is case B, where you find a balance between input and output. Speaker 1: It is there. Speaker 1: That is, we get results proportional to the amount of time and energy we have spent on tasks. Speaker 1: As you can see, being here is definitely better than case A because you managed to break even in case of your effort and output.
Speaker 1: Personally, you're fairly satisfied. Speaker 1: Remember, most people do not get promoted for solving their own problems, but people get promoted for solving their managers' problems. Speaker 1: So here, you take up tasks or projects beyond your defined roles, beyond your core deliverables. Speaker 1: It is where you step up to solve your managers' problems, your organizers' problems, or, you know, your overall team's problems.
Speaker 1: You get promoted for solving your managers' problems and not just your own, as I was saying. Speaker 1: Now you move your paradigm. Speaker 1: There's a paradigm shift here. Speaker 1: You move your paradigm to your team or your managers' paradigm. Speaker 1: This is your I equal to O, where your input and output are fairly, you know, linear.
Speaker 1: The more you deliver these, the greater the satisfaction and your stakeholder satisfaction. Speaker 1: Now finally, coming to where we all aspire to be, case C. Speaker 1: Low input yielding maximum output. Speaker 1: Your graph here is always about the origin in all cases. Speaker 1: Here, you find time not just to work on the core items, but on strategic problems that impact the larger organization and industry.
Speaker 1: This is unexpected from you. Speaker 1: And even the smallest of tasks or projects that you take up and you deliver will delight folks. Speaker 1: Technically, no one expects this from you, so they will not be missed. Speaker 1: But it is when you take up these opportunities that you stand out. Speaker 1: You delight.
Speaker 1: Finding some time and investing your energy in these tasks helps you stand out from your peers. Speaker 1: Now here, you're no longer limited to just your team, your manager's problems, but you're looking at the larger organization. Speaker 1: And in many cases, you're looking at some industry defining changes as well. Speaker 1: And this will help you scale, not just in your role where you are, but apply those same skillsets outside in another role and grow as a leader.
Speaker 1: These will not come to you naturally. Speaker 1: You have to look right. Speaker 1: You have to look left and you have to look and identify gaps to find these problems. Speaker 1: And then you step up proactively to find solutions and drive such differentiating initiatives. Speaker 1: In summary, the features or output we deliver in our careers or professional life is not too different from how we deliver our products.
Speaker 1: Understanding the breakdown of deliverables and carefully planning our time, deliverables and internal careers is key to our growth. Speaker 1: So you'll ask me, Sita, you gave us this framework, but what are some actionable items that we can use to go from case A, that is output significantly lower than input, to our desired case C, output significantly higher than input, to ensure that we work on delighters and stand out.
Speaker 1: It starts with being cognizant and consciously prioritizing and planning your time and tasks. Speaker 1: A few techniques that have worked for me are ruthless prioritization. Speaker 1: It's a good idea to use a framework for this. Speaker 1: In my case, I use the big rock, small rock framework to prioritize. Speaker 1: Now, each one has a mental model to do these, but putting it down as a framework can help us bring more discipline.
Speaker 1: Now, once you prioritize and you know what to achieve, you can go about planning and allocating time to these tasks. Speaker 1: For this, you can use time boxing or Pomodoro or any other techniques that helps you focus and make your tasks time bound. Speaker 1: In the absence of these techniques, I found myself spending most of my time on core tasks and being a case A.
Speaker 1: Now, the second thing that you could do is you could walk into your leader's shoes. Speaker 1: That is, you try to understand their problems and be a problem solver. Speaker 1: Differentiate yourself by making recommendations or suggesting solutions. Speaker 1: When you take a problem, take a few suggestions as well so that you could brainstorm those.
Speaker 1: Shadow him or her in meetings and understand what they're thinking, not just your direct manager, but the others, anyone you aspire to be. Speaker 1: And of course, be genuine. Speaker 1: The other thing that you could do is you have to free up your time on your calendar to get to the delighters. Speaker 1: Here, you can look at things like automation and delegating and mentoring others on these core tasks so that you have a partner and, you know, you can allow others also to scale.
Speaker 1: And this gives you time to move up from your core tasks to your delighters. Speaker 1: And finally, another thing in order to move from case B to case C, finally, is you've got to be looking right and left for opportunities, identifying them. Speaker 1: You have to be in an eternal beta phase, wherein be ready to learn, adapt and innovate.
Speaker 1: Think big picture, think about the connection of your work to other areas and how it can, you know, meet come together. Speaker 1: Learn about adjacent areas to your current work and expand your skill set in those areas to find your delighters. Speaker 1: And a final lesson. Strategic initiatives are in most cases ambiguous in nature. Train your mind to deal with ambiguity.
It's not easy, but you can get there. Be intentful. Speaker 1: So quickly recapping. While building products, the Kanu model framework helps us focus, prioritize and invest an organization's time on features that will make a difference or satisfy customers. Speaker 1: In the same way, we can use the input output framework to measure the value we are delivering to our stakeholders.
Speaker 1: By following the framework, do remember customer expectations. And in your case of in the case of your career, your stakeholder expectations change over a period of time. Speaker 1: So you're delighted at one stage could become a core when you get promoted. Speaker 1: Understanding your customers' experiences and expectations and effectively generating innovative ideas to continue to solve them are important for a product to scale.
Similarly, it is important to be an eternal data, keep evolving and finding new delighters, depending on the needs of your market. Pure wishing that this framework helps you identify, focus and intentfully carve out time for your delighters and stand out to build your USP. Good luck. Thank you.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why hard work alone does not get you promoted, and what does
Qualcomm product leader Sreeja Nair uses the Kano model to show how to move from must-have tasks to work that delights your stakeholders.
In short
Long hours on expected work rarely lead to promotion, because managers judge the output they can see, not the effort behind it. Sreeja Nair, Staff Product Manager at Qualcomm, borrows the Kano model from product management to explain the gap. She shows how to protect time for "delighter" work: strategic problems nobody expects you to solve, which make you stand out.
Key takeaways
Learn product management frameworks to evaluate your personal brand.
Practice strategies to differentiate your personal brand.
Understand how differentiating your personal brand is similar to how you differentiate the products you build.
The promotion that never came
Nair opens with a story many viewers will recognise. About five years into her career, she spent more than six months working very long days on a critical project for her team. She was proud of the result: "I confidently went in for my performance review at the end of the project. I expected a promotion." (2:04) Instead she was told she was not there yet.
She admits she was upset and blamed her manager. She also notes that many people who later become managers find themselves making the same calls because of trade-offs and constraints. Faced with the choice between looking for a new job or looking for answers, she chose answers. She watched colleagues who earned two promotions in three years, and others who seemed to work less but kept moving ahead.
Output versus input
The pattern she found was simple: "It was all about the ratio of output to input." (4:05) She describes three cases. In case A, input is large and output small. In case B, the two are proportional. In case C, a small input produces a large output, which is where everyone wants to be.
The key point is who measures the output. Nair defines it as how your management and stakeholders see your work: "Not what you view it as, but what the world sees of you, what your stakeholders see of you." (4:38) Her own position at the time was firmly case A. She was working hard but not getting where she wanted to go.
The Kano model in brief
The answer came after she moved into product management and started reading about the discipline. The Kano model, developed by Japanese researcher Noriaki Kano, maps how well a feature is delivered against how satisfied customers feel. It sorts features into three curves.
Must-haves are expected: a phone that makes calls, a car with brakes. "We need to have them, but that does not mean our customers will be more satisfied." (9:23) Performance features, such as a laptop's battery life or a car's gas mileage, raise satisfaction in proportion to how much you deliver. Delighters are unexpected features that surprise users. Her example is Shazam, which at launch identified only a low share of songs correctly and still caught on: "People focused not on the failure, but were amazed at what it delivered." (11:20)
Mapping the model to your career
Nair then puts input on one axis and output on the other. Case A matches must-haves: fixing bugs as an engineer, producing collateral in marketing, closing deals in sales. These tasks have to be done, but they never lift stakeholder satisfaction. "Focusing all our time on these tasks makes us cookie cutter." (13:29)
Case B matches performance features. Here you take on work beyond your defined role and adopt your manager's view of what matters. "Remember, most people do not get promoted for solving their own problems, but people get promoted for solving their managers' problems." (14:42)
Case C is the delighter zone: strategic problems that affect the wider organization or even the industry. No one expects this work from you, so even modest contributions stand out. "And even the smallest of tasks or projects that you take up and you deliver will delight folks." (15:57) These opportunities do not arrive on their own. She stresses that you have to look left and right, spot the gaps and step up proactively.
Practical steps from case A to case C
Nair offers four techniques that worked for her. First, plan deliberately: "A few techniques that have worked for me are ruthless prioritization." (17:42) She uses the big rock, small rock framework to prioritize, then time boxing or Pomodoro to make tasks time-bound. Without them, she says, she drifted back to spending most of her time on core tasks.
Second, step into your leader's shoes. Understand their problems, bring suggested solutions along with every problem, shadow them in meetings and stay genuine. Third, free up your calendar by automating, delegating and mentoring others on core tasks, which also helps them grow. Fourth, keep learning: "You have to be in an eternal beta phase, wherein be ready to learn, adapt and innovate." (19:23) Learn adjacent areas, connect your work to the bigger picture, and get comfortable with uncertainty, because "Strategic initiatives are in most cases ambiguous in nature. Train your mind to deal with ambiguity." (19:48)
She closes with a reminder that customer expectations change, and so do stakeholder expectations. A delighter at one career stage can become core work after a promotion, so the search for new delighters never stops.
Watch the talk
"Stand Out: Find your USP" by Sreeja Nair, about 22 minutes: https://www.womentech.net/video/sreeja-nair-stand-out-find-your-usp
About the speaker
Sreeja Nair is a Staff Product Manager at Qualcomm, where she manages the P&L for the Wireless Infrastructure and Networking Enterprise segment and holds two patents in wireless technologies. She is a 2020 YWCA Silicon Valley Tribute to Women Honoree, was named Qualcomm's Global Inclusion and Diversity Champion in 2019, and mentors new graduates and girls entering STEM.
Questions this talk answers
Why doesn't working long hours lead to a promotion?
What is the Kano model?
How does the Kano model apply to a career?
How can you make time for delighter work?
Does a delighter stay a delighter?
Drafted with AI from the talk transcript. Editor review pending.