Kim Hellbom

NEW EERIE-SISTIBLE ROLES ... 🧛‍♀️ HEAD OF DESIGN - Series A - b2b2c - fintech/internal tools - REMOTE - 8-12~ YOE - $170-220K - hands on, then build team. Founding Player-Coach Design Leader. Equity. End to End. Strong UX to visuals, design systems, and brand. Startup experience and leadership experience required. 🦹 FOUNDING DESIGNER - Series A - b2b consumer - AI/ML Science/Edtech - REMOTE - 3-6 YOE - $120-150K - hands on - you'll lead product design, working closely with engineers and users to create impactful user flows, prototypes, and high-fidelity visuals. You'll also contribute to brand evolution. Ideal for someone proactive, detail-oriented, and experienced in fast-paced startup environments. 🧟‍♀️ This one may be more of a trick than a treat 👀 : SENIOR PRODUCT DESIGNER x2 - b2b - hardware/software - NYC onsite 5x a week. - $160-190K - Entrepreneurial mindset. Mix of hardware/software/service design. Shape Design System + brand. Rapidly prototype, improve app UX, scale operations with internal tools, and simplify complex processes, using research and feedback to refine concepts. Hopefully these descriptions came in candy! 🍬 🍫 TO BE CONSIDERED >>> send me your resume + design work and passwords + your LinkedIn page (If I can't find your LI on a CV or portfolio, we will have a problem lol) + your current location regardless if the role is remote. EMAIL: [email protected] - a BRIEF description why any of these roles resonates, (a direct link to a related project is also appreciated but pls do not send me 10 links and pls do not write lengthy paragraphs). THANK YOU!! Due to the volume I receive by EMAIL, I cannot reply to everyone. 👻 Happy Halloween from me and Midnight! He's like a teenager who doesn't want to be in a picture with his mom.

70

2 Comments

I’m a big believer in agile thinking. If your idea can’t move, it’s going to get overtaken in the market… and in people’s minds, too. At Orb, we’ve taken a developer platform approach to the world of billing. Where we can offer the flexibility to make ideas happen on the spot. Things can go from “I have this creative idea!” to “Let’s make it happen!” in the same breath, as opposed to waiting for months for the ship to turn around. A lack of agility can rob even the most lucrative companies of their competitive edge. The last thing I want to say, as a leader, is “Sorry, engineering and product leads! It’ll take 9 months for this wonderful thing to happen.” That’s how good ideas arrive dead on arrival. Excellent ideas don’t wait around.

8

1 Comment

The secrets of how experienced engineering leaders accelerating growth of new Tech Leads... 𝘔𝘪𝘯𝘥𝘴𝘦𝘵 + 𝘗𝘦𝘳𝘧𝘰𝘳𝘮𝘢𝘯𝘤𝘦 𝘦𝘹𝘱𝘦𝘤𝘵𝘢𝘵𝘪𝘰𝘯𝘴 + 𝘚𝘶𝘱𝘱𝘰𝘳𝘵 + 𝘍𝘦𝘦𝘥𝘣𝘢𝘤𝘬 = 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗠𝗶𝗻𝗱𝘀𝗲𝘁 Individual focus → 𝗧𝗲𝗮𝗺 𝗳𝗼𝗰𝘂𝘀 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗘𝘅𝗽𝗲𝗰𝘁𝗮𝘁𝗶𝗼𝗻𝘀 I love Andy Grove's definition 𝘓𝘦𝘢𝘥𝘦𝘳𝘴 𝘢𝘳𝘦 𝘫𝘶𝘥𝘨𝘦𝘥 𝘰𝘯 𝘵𝘩𝘦 𝘰𝘶𝘵𝘱𝘶𝘵𝘴 𝘰𝘧 𝘵𝘩𝘦𝘪𝘳 𝘵𝘦𝘢𝘮𝘴 𝘢𝘯𝘥 𝘵𝘦𝘢𝘮𝘴 𝘵𝘩𝘦𝘺 𝘪𝘯𝘧𝘭𝘶𝘦𝘯𝘤𝘦. Although I prefer to use the term 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀. It's possible for a team to product a lot of output but not much value! 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗮 𝗧𝗲𝗰𝗵 𝗟𝗲𝗮𝗱? A team scoped Tech Lead can have many flavours. Is team leadership included? What about line management? What about delivery? Clarity is key 𝗦𝘂𝗽𝗽𝗼𝗿𝘁 Engineer → Tech Lead is a tricky transition. Holding more frequent 1:1's initially Seek feedback from team Stay close 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 We all make mistakes when taking on new responsibilities  Provide both reenforcing and corrective feedback Observations + Impact = Actionable feedback Learn from mistakes Celebrate the wins P.S How do you support new Tech Leads?

9

4 Comments

Anyone working in a design system team will know there’s lots to do and lots to learn. To celebrate twelve months in my role as Senior Product Manager on the BBC’s WebCore Design System I wanted to share nine lessons I’ve learnt from working in this interesting and complex space. They include.. 📚Design systems are an essential part of modern development and design 📚There’s huge potential for accessibility wins 📚Research is key 📚People are your product too 📚Community matters 📚People love design systems. People hate design systems 📚Demonstrate value and celebrate wins 📚Governance, yes please 📚Metrics ftw As I mention in the article, the design system community is supportive and mega helpful and people have given me a lot of their time and expertise. Shout outs to Steve Messer Ellis Capon Marianne Ashton-Booth Amy Hupe Dan Donald Scott Strubberg Robin Cannon Grace H. and good folks that run zeroheight's Converge Festival for being super knowledgeable and all round good eggs 🥚. If you work in design systems, which of these lessons resonate with you? Or, more importantly, have you got your own lessons to add to this list?

102

12 Comments

I’m loving the direction of the plan comparison chart we just added to the IntegrationOS pricing page: ▪️ Plan names are sticky to keep in view ▪️ Plan names have individual CTAs ▪️ Features are segmented by core product, security and support ▪️ FAQ accordion to answer any stubborn questions

16

1 Comment

If you're doing CRO, have a wee bit of time tomorrow at 10am, I'm going to share the one single thing that I think made my old consultancy sky rocket 🚀 OKRs. In the process, I'll share: ⓧ what the 3 x myths of doing CRO are (revenue, revenue, revenue) ⓧ how to prioritise CRO solutions and why its a problem ⓧ the 30x interviews and research that led me to a solution Join here with House of Performance (hop) and help me beat the numbers for Bhavik Patels previous webinar. (oh, it's on, Bhav) https://lnkd.in/exyhTp3S

55

6 Comments

At No Moss we've been hard at work developing our Guide to Product Discovery: How to Validate Your Product's Business Case. Some great thought starters so read the full piece here > https://buff.ly/4bpjo29 #ProductDiscovery #StartupTips #ProductStrategy #Innovation #MarketResearch

14

1 Comment

For 21 years, the Agile Manifesto has influenced software development. Yet, studies on its real-world impact are limited. Recent insights reveal: 🇬🇧 81% of UK business leaders & 🇺🇸 89% in the USA worry about on-time software delivery. A new study from the book “Impact Engineering” shows: ❌ 65% of Agile projects miss deadlines, budgets, and quality. ✅ Only 10% of Impact Engineering projects face the same issues. Key Agile principles: ⚡️ Working software over Comprehensive documentation ⚡️ Customer collaboration over Contract negotiation ⚡️Responding to change over Following a plan However, projects with documented requirements before development are: 📈 50% more likely to succeed. 📈 97% more likely to succeed with clear initial requirements. 📈 7% more likely to succeed by avoiding late-stage changes. Agile has faced criticism, including the controversial UK Post Office Horizon IT system. But is it time to shift from Agile to Impact Engineering? How would this change your approach to knowledge management and teamwork? Find the book here: https://a.co/d/7Q7LJRV 💡 #SoftwareDevelopment #Agile #ImpactEngineering #ProjectManagement #TechTrends #Innovation #Leadership #Teamwork

7

4 Comments

In case you missed it while prepping for Flag Day 🇺🇸 Happy State of Engineering Management Report Day happened this week! The annual thought leadership piece from Jellyfish has dropped. Hear from Engineering leaders, managers and frontline ICs .... we cover a range of topics that matter to great R&D leaders. Key Points: 1️⃣ Engineers are now strategic partners! 🙌 2️⃣ Burnout continues to be a challenge 😱 3️⃣ The talent shortage is spiking back up. 4️⃣ Many teams have embraced #AI 🧠 5️⃣ Others have legit concerns about AI ⁉ If #developerproductivity #genAI #engineeringexcellence are important to you .... have a read! (link in the Comments)

2

1 Comment

An overlooked reason for upgrading #Umbraco are the #accessibility improvements that it brings to Umbraco Forms. You can read more about them here https://lnkd.in/eNy3z7bi I've also written a few notes on why if you're on Umbraco 8, 10 or 12 you should be looking to upgrade to Umbraco 13 (LTS) or Umbraco 14 (STS) https://lnkd.in/eKmDwAtu #OpenSource #DotNet #A11Y

14

Looking to amend a booking? No problem! Within the Go Catch App you can request to amend a booking, Simply pick a reason from the selected choices and submit to customer support. Remember when requesting a change fishery rules always apply. Need help with anything else? Simply Email [email protected] 📲Download the App 🔐Create your FREE account 📆Book your session 🎣Go Fishing #Catch #GoCatch #CatchReport #Catch22 #Fishing #Angling #Carp #CarpFishing #Carpy #CarpLife #CoarseFishing #CatchAndRelease #DayTicketFishing #DayTicketCarping #UKCarp #BigCarp #Peche #Karp #Karpfen #Karpervissen #getoutside #gofishing

3

Your dev team is under resourced Spoiler - it always will be Don't get trapped thinking if you just had two more (or fifty more) devs you'd be able to work through the backlog and get ahead. The problem is that teams try and filter and prioritise *down stream* on outputs. 100's of outputs. Try filtering and prioritising *up stream* on strategic outcomes that matter to the business (and across the business).

12

8 Comments

"In this three part article we will look into the three exes of technically possible, ethically and/or morally right and legally acceptable and how they can work in tandem or against each other.." It's a good one from Lena Pejgan Nyström. https://lnkd.in/eB-dViZU

3

✍🏼 BACK TO WORK WITH COPILOT IN ONENOTE Hands up if you take scrappy notes whilst multitasking… Try Copilot in OneNote 1️⃣ Create a to do list from the information on this page 2️⃣ Rewrite my notes making them clearer and more concise so I can share them with colleagues 3️⃣ Generate a list of pros and cons from my brainstorming session 🔹 Find it here 👉🏼: https://lnkd.in/g43fSVGh! 🔹 Learn about it here 👉🏼: https://lnkd.in/g7JYxMsv 🔹 Top tip👉🏼: Dictate your notes into OneNote and then use 2️⃣ Have you tried Copilot in OneNote? Comment below! #Copilot #Productivity #AI #Microsoft365 #BackToWorkWithCopilot #MicrosoftUK #MSFTAdvocate

4

Just got a chance to listen to Laura Tacho's talk from LeadDev London, "Measure for Change" covering why you need both qualitative and quantitative data when measuring #developerproductivity. When people measure developer productivity, it's often for the reason of reporting the measurements upstream to make someone above them happy, and to validate that they're doing their manager/director/VP job well. 𝗪𝗵𝗮𝘁 𝗺𝗲𝗮𝘀𝘂𝗿𝗲𝗺𝗲𝗻𝘁 𝘀𝗵𝗼𝘂𝗹𝗱 𝗯𝗲 𝘂𝘀𝗲𝗱 𝗳𝗼𝗿 𝗶𝘀 𝘁𝗼 𝗳𝗶𝗻𝗱 𝗼𝘂𝘁 𝘄𝗵𝗲𝗿𝗲 𝗶𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁𝘀 𝗰𝗮𝗻 𝗯𝗲 𝗺𝗮𝗱𝗲, but the improvements themselves must be made by the people doing the work, not those observing them. "We want teams to use data, not just view it. We can do that when we mix quantitative and qualitative data together, because what we don't want is numbers without context..." By involving teams in the measurement process, and giving data back to them, you can drive real change, as opposed to working from a metaphorical box in the sky to report to someone even further away from the work being done. https://lnkd.in/gvK3fX7H

18

2 Comments

Discovered a valuable framework for prioritising product features, developed by Julian Boot . It categorises features as market expectations (filling gaps), differentiators (unique twists on existing features), and exceptional features (driven by customer insights). By plotting these against complexity, we can prioritise exceptional features that exceed expectations and drive business results.

23

1 Comment

3 easy, simple tips to avoid letdowns This story has become all too familiar... ▶️ Teams appear prepared but struggles in projects ▶️ Require redesigning even though they seemed enough ▶️ More difficult conversations with stakeholders How do I know this? I've encountered it over the past 7 years, speaking with hundreds of customers. Here are the 3 simple, easy tips: ------ TL;DR 1️⃣ Immediately, get pricing out of the way 2️⃣ Spend less time talking about requirements, more time on expected outcomes 3️⃣ Share your current situations and challenges ------ In-Depth: 1️⃣ Understand if your budget aligns with the vendor; remember, you often get what you pay for. Vendors can't perform miracles. 2️⃣ Discussing features is okay, but solving your problems are ♾️ more important- especially if you're unsure what you need. (Tip: Most customers don’t) 3️⃣ Maximize your vendor’s expertise. More sharing means more tailored advice. Less sharing, more general advice. ====== P.S. Was this helpful? If you know someone who might need it, please share. It also helps me understand the type of content you find valuable.

5

2 Comments

Do you have a React Native app and want to extend your app into the land of Vision OS? Well look no further than this wonderful little package https://lnkd.in/eGrjCe2K (I have no affiliation). It definitely isn't ready for production use but it's a great step forward in bridging the gap and bringing React Native and VisionOS closer together. I will try it out and share some findings... I feel like I have to because I am doing literally nothing else with my Vision Pro. #ReactNative #VisionOS #Development

8

1 Comment

Interesting take by Theo on Dan's talk from #React Conf. If you haven’t watched the original one, you have to watch this one - yes, it’s an hour long, but I’m sure you can find 45 minutes at 1.5x speed during the week. Dan covers some groundbreaking concepts that are set to shape the future of React development, and these ideas are too important to miss. Honestly, I would even play it at a dev team meeting at work. It’s a great way to get everyone on the same page about where React is heading, and this talk is an invaluable resource for anyone planning to work with React in the next few years. https://lnkd.in/dmtgxWAw nSoft

3

1 Comment