If you're interested in the subject of why models with car works and other techniques over used in most advertising media check out "Influence the Psychology of Persuasion".
It's possible to catch yourself recommending or telling a story about a product you heard about from a friend. You think a friend told you, but then you realize after seeing a paid ad for the product it was a memory created by you. Disturbing when you realize it happens.
I think we made a big mistake trying to convince everyone that the digital life is like real. E.g. you can have real conversations etc. (they are real but not the same, maybe our discussions online are too real idk), please bear with me ...
IMO there has been a huge interest by Tech to make everyone believe that Online life is very much like real life, for some of us it even did become so (SecondLife, gaming, etc). And there are many calls to enforce real-name policies and to outlaw anonymity in Tech. The theory is that this will improve authenticity, get rid of trolls ("if only we could back this with more security, root of trust", etc).
But when I just judge from myself, how I use the web ... I am not actually "really me" in the same sense. Even posting under my real name I often catch myself having provided some kind of snapshot of my inner state of mind or general feeling, and which to my horror shouldn't be taken at face value (yet it is because I said it and it is written).
When speaking pseudonymously it allows me to air half-baked thoughts and feelings so that I can get feedback (in a safe way) and then allows to improve my thinking on the subject.
I wonder would I say the same things under my real identity ? and the scary answer is sometimes I accidentally do. And I guess others also make these mistakes. Compartmentalizing is really hard and once I said shit the cat is out of the bag ... what was written may haunt me forever.
Getting judged by a prospective employer wading through our social media footprint is already reality, and before entering some countries I have to unlock my phone now. None of this is supposed to be like that IMO because we humans don't compartmentalize our thoughts the same way when we are online as we do when we have a conversation IRL
What tricks us into thinking that "just because we say it we should stick to it", because we use the written form. By saying it in our head and WRITING IT DOWN, it becomes very hard to take a step back and retract our position. Writing things down is one of the keys in how we commit to something according to Robert Caldini[1]. And because we usually write online our not well thought out positions (spitballing), we end up making these spitballs our personal hills to die on. This is something we haven't yet realized: ONLINE != IRL, yet we want to force people to believe it is the same.
[1] Influence: The Psychology of Persuasion https://www.amazon.com/Influence-Psychology-Persuasion-Rober...
These things come with experience over time, but the fact that you've made it far enough to ask the right questions in the right place to ask them is 90% of the journey.
I realize this sounds cliche, but I can't stress enough that health comes first. I would make the following a priority if you feel you're not taking as good care of yourself as you should:
Eat reasonably healthy (just avoiding junk food is enough, no need to go overboard)
Get enough sleep (and eliminate whatever habits get in the way of that) - Without enough sleep, your mind will in subtle ways try to put the least amount of effort toward doing things. This is especially dangerous if you are trying to counteract those effects with things like caffeine or stronger stimulants.
Don't do anything stupid to harm your body. Contrary to popular belief, you are not a Zerg mutant with infinite bodily regeneration capabilities. It will catch up to you sooner than you think it will.
It's quite hard to improve one's mental habits when not in the best shape (but if you fucked up early on like I did, it's never too late to make things better).
Assuming you're already doing all that, I'll speak specifically to your post:
1. Don't burn yourself out, especially for a job you don't enjoy.
Not a mental model per se, but more of a disclaimer that I highly advise against pursuing such efforts unless you feel the company is a good fit for you. I've personally found that being successful at a company depends as much on the company as it does you. All the talk about culture fit applies here (though I personally hate the terminology). Sometimes you can adapt to environments that are challenging, but sometimes that can be a case of learning bad and toxic habits. And sometimes, no matter how much better you think you perform, it won't improve your job security. So you have to first understand whether you're really happy in that environment. Don't burn yourself out to try to get ahead of the technical debt curve just to try to earn some job security in an environment that you don't feel at home with in the first place.
2. Document what you're going to do, and why, before you start doing it.
This doesn't mean you can't amend the plan when you see a reason to, but your technical changes should be driven by your written plan, and nothing else. If you don't do this, the complexities of the technical systems you're touching will bleed into the mental model you've set for yourself with what you're trying to build. You'll exert subconscious effort to try to maintain some grounding, but inevitably you'll slip at some point and end up doing too much or too little changes. Then you may exert significantly more effort trying to explain to your peers or boss why you spent extra time building something that has no apparent need, especially these days with the plague that is Scrum (fragile, not agile).
You don't necessarily have to do this for all of your work, but deviating from this procedure should be the exception and not the rule.
3. Avoid band-aid workarounds
Always fix the root cause! Always! Okay, there are times when this is not possible. Sometimes, the root cause is part of a piece of legacy software that can't be modified easily or at all. Sometimes the problem is with a closed-source library, an API, or data feed from external partners. It's okay to do workarounds in those cases, but you should be extra vigilant for the pros and cons of doing it. Make sure the business, not just your Scrum Lord, is getting a real benefit from seeing it done. In any case, when doing a workaround, it's wise to include detailed documentation in the appropriate places as to why that workaround exists, or it will contribute to the pain, suffering, and burnout of future members of your team. While this can happen to companies of any stage or size, the real danger zone here IMO lies with companies in the Series B range, as hacky throwaway code could be done with no consequence before then, and is even somehow encouraged by some as a best practice for early stage companies.
The other major exception to this is emergencies, involving downtime, prevention of downtime, or other significant operational incidents. However, meeting the deadline for your Scrum sprint is not an emergency. If your boss can't be convinced to understand this, your choices are to do a better job of convincing, invite them to convince you otherwise (they may succeed!), or to find another place to work. If something is time-critical for business reasons, it's your product manager's job to inform you of that.
If your job feels threatened even slightly by the concept of missing sprints, then you must make it a priority to resolve that, because even the presence of that feeling is itself a good reason for the job to be at stake, as it's indicative of critical communication problems with your immediate team. And it most likely isn't your fault but rather just a failure of the team as a whole (though you have the most power to do something about it regardless of the root cause). It is a growing pain that can be solved, as long as you're not working with assholes.
There is one time where this no-bandaid rule must be broken when you are short on time, but you should work to avoid having ever happen in the first place. If the business you work for (via CEO, PM, whoever) is mandating a hard deadline for a given feature, then you probably should err on the side of getting it done ASAP. If you are in this situation, don't panic. See if you can work it out with your team to spend time after the release to ensure that technical debt is manageable and things are working reasonably smoothly after some code polish. You can prevent some of these scenarios in the future by having a maintainable codebase, and you get a maintainable codebase by reducing technical debt, and you minimize technical debt by not implementing band-aid solutions to appease Scrum Lords. To put it simply: Business deadlines are real, but Scrum deadlines can amount to a hoax. Refer to this article to see Scrum actually addressing this problem: https://www.scrum.org/resources/commitment-vs-forecast
Another thread/post regarding technical debt: https://news.ycombinator.com/item?id=19850629
4. Maintain Good Relations and Build Influence
Building influence will make it easier to succeed in virtually all tasks, big or small. I can't recommend quick wisdom on this one, but could point you to a few good books (or audiobooks if you prefer). Takes years to learn this. I personally prefer to allow time to digest and sleep on the knowledge gained from books, though others (notably Bill Gates) swear by the method of binge reading.
https://www.amazon.com/Influence-Psychology-Persuasion-Rober...
https://www.amazon.com/48-Laws-Power-Robert-Greene/dp/014028...
https://www.amazon.com/Principles-Life-Work-Ray-Dalio-ebook/...
https://www.amazon.com/Extreme-Ownership-U-S-Navy-SEALs-eboo...
I decided to spend a good chunk of time writing this as I start a new job which I really hope to be successful at, and I want to reinforce and review what I think will lead toward that goal. But I hope this is found to be useful to others too.
It's not about sales it's about how people think, act, and make decisions. I would bet that most any book on sales will invariably touch on at least some of the topics covered in this book.
It's a fun read and I promise you will start to see these patterns being used in everyday life in verbal and non-verbal communication.
Humans are predictably irrational, there are mountains of scientific evidence on the topic [0, 1].
The industry plays us like fiddles to get us to consume ever more. There are more parameters than the ones I described above (socialization and long term hormonal effects come to mind), but the growth of the food industry is the main driver behind the obesity epidemics.
All that food has to be bought, otherwise there's no growth, and investors are not happy and they put their money elsewhere.
The easiest way to convince people to buy food is to make them want to eat it. Modern food has been engineered and optimized to be deceptive and take advantage of our instinctive and cognitive biases, in order to get us to eat more than we need to be healthy.
0. https://web.mit.edu/ariely/www/MIT/
1. https://www.amazon.com/Influence-Psychology-Persuasion-Rober...
Anchoring comes in many forms (and in asking questions like a survey should be carefully avoided) but one such form is when a person is shopping and being helped by a store clerk:
You're looking for a nice dress watch. Mentally, maybe you're hoping to spend around $300. You ask the clerk to show you some watches. They bring you to a $2000, very nice watch, but that's far more than you wanted to spend. So, next, they bring you to a $500, also very nice watch. Your expectations have already been anchored to a $2000 price tag, to this second model, at a quarter of the price, seems like a really great deal. You think maybe your $300 target was actually too low for what you're looking for, and perhaps spend the higher price.
[0] https://www.amazon.com/Influence-Psychology-Persuasion-Rober...