๐ ๐ฎ๐ฑ๐บ๐ถ๐ฟ๐ฒ ๐ฐ๐ผ๐บ๐ฝ๐ฎ๐ป๐ถ๐ฒ๐ ๐๐ต๐ผ ๐๐ฒ๐น๐น ๐๐ ๐๐ต๐ผ ๐๐ต๐ฒ๐ ๐ฎ๐ฟ๐ฒ At GitHub years ago, like clockwork, team members would ask the question during our Company All Hands about the contract with ICE (Immigration and Customs Enforcement). The company would often give equivocating answers in the early days of the discussion. Microsoft later released a statement about how they handle military contracts (they don't turn them down). But the questions kept coming. Then one day the leader of GitHub answered the question something to the effect of "look, we are doing this contract, per our stated policy. It's not changing. If you don't like that, maybe GitHub isn't the right place for you." That is certainly not a direct quote, but it was the overall gist of the statement. It was a great moment because it made things much more clear. Regardless of which side of the discussion you leaned towards, you had clarity on what the future looked like and who GitHub was. I love when companies tell us who they are. Coinbase and 37signals made public declarations about who they are and what working there would be like. Regardless of whether or not I agreed with their "no politics" stance, I loved that they were telling people, explicitly, what they were about, regardless of the blowback. People want clarity. Your teams want clarity. Providing that clarity is better for everyone. It's better for the people who realize the company may not be a good fit for them any longer. It's good for the people who stay who no longer have to deal with ambiguity, or hear the same questions repeated because the answers are not clear and direct. It galvanizes the future direction of the company. Of course the decision may not be the correct one. That's a different topic. But it sets a clear path in a clear direction. While if those companies made the right decision is up for debate for many, my purpose is to primarily praise companies who have a clear, communicated vision. I admire that about the companies mentioned earlier. They told us who they were, and gave people the clarity to choose if that was something that brought them to the company, or pulled them away. Many companies try to walk the tightrope. I think that is the worst place to be. Having clarity is priceless.
Matthew Duffโs Post
More Relevant Posts
-
I love this explanation. A great read.
Diversity, Equity & Inclusion Strategist. Bestselling Author of Reconstructing DEI and DEI Deconstructed. They/Them. LinkedIn Top Voice on Racial Equity. Inquiries: lilyzheng.co.
"I understand that a more operationalized definition of #equity is useful, Lily, but what's wrong with that graphic of people on boxes? Isn't it at least a good way to start?" This is a good question, and I have a strong opinion on my answer. The people-on-boxes graphic to illustrate equity is a poor representation for how modern equity work actually looks in organizations today. Its inaccuracy results in a heavy risk of activating the threat response of those with privilege to engage in completely avoidable defensiveness, and for this reason, I sincerely believe that using it as a teaching tool may be doing more harm than good. Let me explain. The people-on-boxes graphic illustrates two core principles of equity work: a focus on outcomes (the need to see the ball game) and the recognition of differences (the people's different heights). But the story it tells about inequity and its solution is both inaccurate and dangerous. In the graphic, inequity is a wooden fence, and solutions to inequity are boxes. Equity, according to this graphic, means recognizing that some people don't need any resources, others need some, and still others need a lot. If this graphic were applied literally, moving from equality to equity would be convincing the person on the left to give up their box to the person on the right, arguing that they don't "need" their box to see the game, but that the person on the right does. Okay. Let's apply this same approach to a workplace inequityโhow about "inequity in promotion opportunities." Applying this metaphor might mean seeing the inequity as "an opaque promotions process," and the boxes as "networking time with the manager." Moving from equality to equity would be convincing those with the most privilege, like white, cisgender men, to give up their networking time with the manager to those with the least privilege, like queer, trans women of color, arguing that privileged people don't "need" this networking time to get promoted, but marginalized people do. This is NOT what equity work looks like. In fact, this zero-sum metaphor is one of the most dangerous ways to describe this work, and routinely shows up in misinformation used by anti-DEI groups to activate the defensiveness of people with privilege. Outcomes are important. People are different. But equity work is NOT about a zero-sum redistribution of resources, but rather a changing of the environmentโthe systemโto meet everyone's needs and sustain or improve benefit to everyone. By devoting resources to fix systemic issues, rather than compensate for them through disparate (and perhaps now *illegal*) treatment, effective equity work not only presents more enduring solutions but enables everyoneโwith any mix of privilege and marginalizationโto feel like they directly benefit. This is the reality we have to be teaching. And while no infographic is perfect, if we're going to use infographics to teachโthen please. Let's use better ones.
To view or add a comment, sign in
-
-
๐๐ผ๐ ๐๐ถ๐บ๐ฝ๐น๐ฒ ๐ฎ๐ป๐ฑ ๐ผ๐ฟ๐ด๐ฎ๐ป๐ถ๐ฐ ๐ฎ๐ฐ๐ฐ๐ผ๐๐ป๐๐ฎ๐ฏ๐ถ๐น๐ถ๐๐ ๐ฎ๐ป๐ฑ ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐๐ถ๐๐ถ๐๐ ๐ฐ๐ฎ๐ป ๐ฏ๐ฒ At Spoonme we believe in lightweight process and high levels of trust. We try to communicate well, but have as little overhead as possible. Here is an example of our simple way to keep each other up to date on what we are doing. This is my update for this week. You can see it is focused around actually shipping, not just saying I am working on stuff. I am trying to link each update with a tangible (virtually tangible!) thing that I have shipped. In these cases, they are pull requests for our iOS app we are releasing (maybe this week?). I add to this during the week. On Monday morning we have our (only scheduled) meeting of the week and take the first 5 minute to read through everyone's weekly update. Then we discuss what we are working on that week, and if we learned anything the previous week that changed our focus or priority. It's simple, but I believe it works. This represents about 10 minutes of writing per week, and a 30 minute meeting on Monday. In exchange we build accountability and communication into our week in an incredibly lightweight package. My goal is to hire a small group of people who are very talented at what they do, build an app and experience that feels like art and magic as much as software, and build wealth for our team and food creators. We are barely on the first step of that journey, but it's been incredibly rewarding to work on solving these problems with a small team of kind, talented people. We don't have formal backlogs (hat tip to 37signals and Jason Fried for Shape Up, which was highly influential for me). We try not to waste people's time with meetings (Sahil Lavingia was influential here). We identify the problem we are trying to solve clearly, and let people use their judgment, experience, and skill to solve it. My biggest hope is that we get to stay in the game for a long time and keep building.
To view or add a comment, sign in
-
-
๐๐ก๐ข๐ง๐ค๐ข๐ง๐ ๐จ๐ ๐ช๐ฎ๐ข๐ญ๐ญ๐ข๐ง๐ ๐ญ๐จ ๐๐ ๐๐ง ๐๐ง๐ญ๐ซ๐๐ฉ๐ซ๐๐ง๐๐ฎ๐ซ? ๐๐ง ๐ฎ๐ฉ๐๐๐ญ๐ ๐จ๐ง ๐๐ฉ๐จ๐จ๐ง๐ฆ๐ TLDR: We've been building Spoonme for 9 months and are a few weeks from releasing our mobile application. I've spent about $160,000 on the business, and more in personal expenses. It's been quite the risk, but I decided that I would consider earning a fat paycheck while working for a large company, but never trying to build my own business, a much larger failure than trying to build my own business and failing. Even if I burned $500,000 trying it! I am grateful I have been able to chase this dream these past 9 months. We have a great product and tech foundation, and hopefully the product we have been building resonates with people when we release it. Long version: In July of last year I found myself in a position where I could try something I have wanted to do for about a decade: leave my job and start a startup. I had funds to self-fund the startup (my preference over VC money) and I believed I had enough experience where I could make something people loved. My goal was to make a product that felt like art as much as it did a very useful tool. I took the leap. We've been building since late August. I hired a contractor to work with me building our backend in Elixir (with Phoenix). The end goal of our app is a cross platform experience (mobile and desktop browser), but I would estimate about 95% of our use will come from mobile. We built for the web at first because we could iterate more quickly while we were in the discovery stage. This was a good idea for speed of iteration, but not the right choice for getting meaningful customer feedback. We hired a designer but ended up redoing the design with a fantastic agency. I'd say if I did the last 9 months again I could have shaved about 3 months of work off that schedule through lessons learned. I had fully internalized shipping to customers early, but we shipped a (poorly designed) web app, not the mobile app. The mobile app should have been the focus from the jump. Right now we have a team of four, with another iOS engineer joining tomorrow. We have built a great foundation from a backend perspective, and are close to releasing our mobile app (submitting to App Store on May 17th). We did this with the three contractors working about 25 hours per week. Constraints require individuals and teams to focus. I've formed a belief that almost all companies are too large. Almost every company is unfocused. One of my main thesis' about starting Spoonme is that a small group of humans can out ship ๐ very large companies, and can make a far better product. That comes through focus. I can't wait to see how users receive our mobile app and iterate to a small, but highly profitable, company. Follow me to see how the journey goes. I am willing to spend every penny I have to make this successful. What lessons did you learn before your release?
To view or add a comment, sign in
-
-
Many of us in Littleton would love to see someone join in this role who has experience in #multimodaltransportation and creating #safestreets. Public sentiment has changed in our city and I believe Littleton can do some really innovative (for the USA) things moving forward. Share with those you know.
Come be my partner in the incredible community of Littleton Colorado! Let me know if you have any questions. The City of Littleton is seeking an experienced Public Works & Utilities Director to lead, plan, coordinate, and direct all the operations of the Public Works & Utilities Department.
To view or add a comment, sign in
-
Great read. I believe these are all "we are trying to help you think through this deliberately" and not be shady to get people to not cancel. Great approach. I also love Jason Fried's and 37signals's mentality of making it a pleasant experience to off board so when a need arises again you think positively of that organization and consider them again to solve your problem. And because it's a good human thing to do.
*Steal this brilliant move from Canva* I went to cancel my Canva for Teams account today -- but Canva's cancellation flow was so good that I changed my mind. And, no, it wasn't because they made me jump through hoops. Things I โค๏ธ: 1๏ธโฃ They reminded me that I have an amazing deal. I still pay $12.95/month, but prices have increased to $29.99/month. I'll lose my deal if I cancel. This is how you turn a price increase into a marketing tactic. 2๏ธโฃ They created loss aversion by reminding me of the premium features I've put to use. Did I really use the background remover 622 times? Why?! (I mean, it is genius...) Loss aversion is a big part of why reverse trials work so well, too. After you've tried a premium feature, you become much more hesitant to lose it. 3๏ธโฃ They made some clever UX choices that subtlety influenced my decision. "Continue cancellation" is in a bright red button -- aren't you NOT supposed to click on the red button? Keeping my plan felt as simple as closing out an unwanted pop-up. --- You got me, Canva! Now this is how you do PLG ๐๐ ๐ For more PLG tactics and insights, subscribe to Growth Unhinged -- my free weekly Substack newsletter https://lnkd.in/exTbjKaM #plg #product #ux #growth
To view or add a comment, sign in
-
-
I strongly agree with this approach to seek out the risk. The most savvy buyers, at the world's largest companies, recognize the sales teams who understand risk and actively look to mitigate it for them, vs the ones who sweep it under the rug. Lean into proactively identifying the risk, and creating a roadmap for the customer to overcome it. From an SE or Professional Services perspective, you help connect the dots for how they will adopt the product after the deal closes.
CEO at pclub.io - Skill Transformation for Revenue Teams. Trained 11,000+ sales professionals and leaders. MSG ME if you're looking to upskill your SaaS sales or revenue team.
Sales Leaders: You have 13 selling days in Q1. 90% of your AEs try to AVOID risk at quarter-end. They think they can sneak risky deals under the radar. They're wrong. The best AEs SEEK deal risk. Here's 4 traits that separate great AEs on March 31: 1. They SEEK risk in their deals. The best salespeople scrutinize their deals. "What would derail this thing?" they ask themselves. When they find an answer, they take action to mitigate it. The worst salespeople don't want anything to do with that. Deep down, they know there could be risk. But they'd rather avoid it than confront it. But don't forget: Reality has teeth. You can't run from it. 2. They "bring up" unmentioned buying process steps. Legal review. Procurement review. Security review. Uncovered decision makers. The best salespeople ask their champions about these things. Even if the champion didn't mention them as part of their buying process. Great salespeople know champions don't always know their buying process. So they ask about key areas they may have left out. 3. They actively ask buyers what would derail the deal. When a deal is trending well, they don't rest on their laurels. They don't just assume it's going to close on time because the champion said so. They make their champion THINK: "Looks like we're trending well. But if something did derail us from here, what do you think that would be?" 4. They shoot their shot with "long shot" deals. When they have deals that have an uncertain timeline, they still ask for the close: "What conditions would have to be true for us to move forward together by March 31?" They're not pushy. But they know their COULD be a shot at closing on time. So they ask what conditions would have to be met to make that happens. Often, they don't get an answer they want to hear. But... sometimes they do. P.S. Closing deals has never been harder. Purchase cycles are more complex. Decisions are made at a higher level. Buying committees are bigger and more risk averse. Win rates have dipped far below what they once were. If you want to join almost 100 SaaS companies (like Hubspot, Gainsight, Blackbaud) upskilling their revenue teams and boosting win rates, talk to me here: https://lnkd.in/g2CkE295
To view or add a comment, sign in
-
I am hiring an iOS engineer to work with us on turning Spoonme.kitchen into a native iOS app. We have the features and functionality determined and in use. Now itโs time to go native. Details in the linked page. https://lnkd.in/gfCdk8PN
To view or add a comment, sign in
VP of DevOps Engineering Enablement
1yThe first principle of leadership is to create clarity. Dancing around the difficult topics can only create more problems.