I want the company/ product/ team I support to be a success and if that happens I expect to benefit as a result.
I want to personally be successful, irrespective of (and sometimes at the cost of) the company / product / team I support
The former attitude is the idea attitude for your team to have. However sadly people with this attitude often get overlooked.
Instead the latter attitude often dominates. It’s typified by politics and self interest, and is often a zero sum game.
The fact that the best performing people are often kept in those roles for longer weirdly benefits the more ambitious but less capable people as they will often claim the work of others as their own.
It also weirdly benefits the company (in the short term at least) as they keep good people in high functioning delivery roles for longer, while move the more personally ambitions but probably worse performing people into management roles.
The above cycle is the very epitome of the Peter Principle, where people are “promoted to the level of their own incompetence”.
Often “Peter Principle” leaders will point at the market salary for their roles when negotiating pay rises, rather than the their personal performance or the positive impact they’ve had on the company, product or team.
It’s obviously important not to pay people under their market value. However their market value should be set based in their contribution rather than their titles.
People who really care about the contribution they are making generally don care about titles as they fee hollow and unrelated to their value and impact. Ironically this leads to those same people being underpaid, because of the above cycle.
A lot of ambitious people will start by negotiating a more important sounding title, irrespective of whether they have the ability or impact that comes with said title. Once you have the title it’s easy to claim you’re being underpaid in comparison to peers with said title.
As an aside, as long as design leaders report into product leaders, our ability to influence will be limited. We run the risk of being a tool ambitious product leaders use to increase their influence (my team did this), and an excuse when things go wrong (design did that).
Just a reminder that whenever you give somebody on your team a promotion the rest of the team will evaluate whether the promotion was based on merit or politics, and act accordingly.
If you clearly promote on merit, it will ideally encourage others to follow said behaviour.
However did people see promotions happening based on politics, their performance will drop, and they may either choose to leave or start playing politics themselves.
This is one of the reasons why progression frameworks are so useful as they clearly demonstrate the behaviours the organisation expects in order to promote people. Just be aware of people optimising solely around these behaviours and nothing else, as people can game the system.
I’ll also add that nothing demotivates a team faster than realising that all the hard work they’re putting in is simply going to advance the prospects of their boss, rather than having a tangible improvement on the company, product or team.
As such, under performing teams (full of great people) are often the result of managers who are more interested in playing politics and self promotion than delivering results. Sadly these sorts of managers will frequently blame their teams for this lack of performance.
People with the wrong sort of ambition will attempt to claim personal credit in interviews while laying poor performance on other people shoulders. Frustratingly this tactic plays well in an interview setting.
Conversely people with the right sort of ambition will give complex nuanced answers here. They’ll share successes around the team while explaining failures in a way where they’ll take some culpability.
As such, interviews tend to vastly benefit individual players versus team players. If you’re a recruitment manager, make sure you watch for this sort of bias.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The model for proving identity by showing a paper bill from a “trusted” provider (utility, bank, council tax) really does fall down in a world where companies have stopped sending paper statements and moved everything online.
I was just trying to pay a bill to @BrightonHoveCC and they asked for two proofs of address that were less than 3 months old. I literally only get two paper bills now. One from the water company and one ironically from @BrightonHoveCC for my council tax. Both are annual.
I have to admit that I find it a little funny that @BrightonHoveCC will accept proof of address from @BrightonHoveCC in order to pay a bill to @BrightonHoveCC. All very Kafkaesque 🤣
There was a time when PMs mostly transitioned from other roles so were often re-titled project managers or BAs.
I have a feeling a lot more people are entering the industry as PMs. Curious whether they are coming from dedicated courses or are more general business graduates.
Most of the new designers I see already had design skills when they join as there are plenty of degree courses out there teaching design, and it’s something you can technically learn on your own, creating portfolio sites for yourself or for friends and family.
Most Product Managers I meet have good business sense but poor product sense (i.e. what makes a great product).
Conversely most Designers I meet have great product sense, but poor business sense (i.e. how can this product make more money).
When you combine these skills the best outcome is a great product which makes a tonne of money. The worst outcome is obviously a poor product which underperforms financially. It's slightly worrying how often it's the latter and not the former.
Usually because the PMs (and more often their execs) are driving the product experience, while the designers are resisting having anything to do with something as crass as making money.
Quick question. Have you ever raised a UX related “bug” in a product you use and had somebody come back to you X months later saying it was fixed?
If teams had to report back to customers on the issues they raised I think a lot more problems would get addressed.
Especially if there was some team metric around this? e.g customer satisfaction around the speed and quality of fixed issues.
I’m sure teams must do this but I’ve never been on the receiving end of one of these.
Last year I flagged up a bug to @firstdirect. The CX person told me that they “took the issue seriously” and were “working hard to fix it”. I asked them how long this bug had been on their backlog for and they replied “over a year”.
One of the main reasons start-ups fail is because they end up solving problems not enough people have, or at the very least don‘t feel strong enough about to justify switching from their current (often free) solution to the startups (marginally) better (but more costly) solution.
Them: “I don’t understand why more people aren’t singing up. Our $20 per person per month solution is clearly so much better than the free Excel spreadsheet they’re currently using”
Me: “How?”
Them: “Er” thinks a minute…
Them: “It has this cool dashboard feature, sends you a notification when something changes and integrates with these 3rd party apps”
Me: “They currently get most of this already through Zapier”
Them: “With our tool they don’t need to use Zapier anymore”
As a designer I grew up believing that talent was everywhere but money was rare, largely because I was lucky enough to be surrounded by super talented but largely underpaid designers. It was only later in life I came to the realisation that talent was actually the rare commodity.
Coming from a working class background, it's understandable why I grew up having this impression, as I really didn't come into contact with people who had money.
The "posh kid" at my school lived in a house they actually owned, rather than was owned by the council. His dad worked in an office rather than a building site and they had holidays in Florida rather than caravanning in Cornwall.