Dustin Senos

A hard requirement when developing a kiosk's user interface is a "Reduced Height" or "Wheelchair" Mode". Interactive elements have be reachable, so they can't be lower than 40cm or higher than 120cm from the floor in Canada.

11

2 Comments

UPDATE: I fixed the link! I recently created a new model for self-hosted Multisite, using GitHub Actions and DDEV for live and test environments. Check out that matrix!! https://lnkd.in/e3tJU59M #drupal #hosting #cicd #qualitycontrol #continuousdelivery #ddev

21

7 Comments

Remote work enabled me to hire an expert team of UX designers and researchers dispersed across Canadian cities. It allowed me to support employee wellbeing so that precarious child care situations, creative passions and needs at home could be balanced with flexible work. We never missed a deadline; our work was always of a top quality. I could hire for the best talent and recruit from outside government. I couldn't offer the pay of private sector, but I could offer a healthy work environment and flexibility - something which many creatives (and folks in general) covet more than money. A slow creep to the end of remote work will make this impossible for many managers working in the federal government in IT. And equally, it will make it hard to retain managers and executives who are also subject matter experts in the field. It's really disappointing to see, and I hope there will be flexibility given so that we can retain the best talent in house. When you foster a work environment that is enticing to IT talent, you build real functional IT capacity within the government. Haven't we learned from ArriveCan? #DigitalGov #IT #remotework #returntowork

114

Company website blogs and resources often fly under the radar when it comes to education and inspiration. So I wanted to shine a spotlight on Instacart Design Blog that I unexpectedly dove into. In just a few days, I've delved into 5 articles that hit the nail on the head, covering topics like designing content with purpose, practicing inclusion in your design team and mastering conference talks. If you're looking for valuable insights and practical design advice, check it out here: https://lnkd.in/gseR8hSh (they've also got a Tech Blog). #JuniorFriday #DesignReads #DesignResources #SharingIsCaring #DesignCommunity

34

one thing that often doesn't come up in these discussions is the need to layer decision-making. if you start the process with high fidelity mockups, you are essentially making all different types of decisions at once: decisions about creative vision, information architecture, flows, and content. it is almost impossible to get clear feedback in that type of situation. ime, breaking the design artifacts down in a way that allows the team to align on one aspect of the broader design approach makes the entire process more manageable and encourages better decision making. this doesn't necessarily mean wireframes. it could include things like: *brand messaging architecture to identify tone and creative vision *content model to identify structure and priority *style tiles or mood boards to explore visual brand identity etc each decision creates a healthy constraint for the next layer of exploration. then, by the time you get to the high fidelity mockups, the majority of the high level decisions have already been made.

10

If you're a designer trying to get up to speed on a new team or project, check out this quick talk based on a recent blog post I wrote for Lab Zero Innovations Inc. (https://lnkd.in/gDw4bR8Y)! Have you picked up any tips of your own? Let me know, or—if you're looking for a designer who's prepared for situations like these—reach out to us at info@labzero.com! #designteam #designteamwork #designthinking #productdesign #uxdesign

11

1 Comment

Really annoyed at Figma's price gouging here. There is no reason other than greed: https://lnkd.in/gfdrEiWH Oh, and I emailed them about it and this line from their reply was particularly poignant: "Additionally the minimum for enterprise is a $5k invoice minimum. 6 enterprise seats or made up with other products." To put that in context... our monthly Adobe bill (for 8 CC, 7 PS, 6 Acrobat licenses) is ~NZ$2k... Amazing how quickly enshittification sets in... #Figma #Design #SoftwareLicensing

8

3 Comments

"Delight" often gets a bad rap when mistaken only as animations, sound effects, and confetti. Here's how I think about delight and its sibling, utility: Utility is the VALUE a user derives from interacting with your product. Value warrants the product’s existence and, much like profitability makes a business sustainable, utility makes a product sustainable. ↳ Utility creates loyalty. Delight is the SATISFACTION a user derives from interacting with your product. Whereas utility is “I need to use this product”, delight is “I want to use this product”, and in the best cases “I want others to use this product too.” Maximizing delight translates to higher app ratings, increased NPS, stronger brand affinity, and increased virality. ↳ Delight creates advocacy. Design, Product, Engineering must work closely to put utility first. But each of these — Design in particular — must also advocate for delight to transform product value from “need to” to “want to.” Prioritizing delight is another form of slowing down to speed up. Small investments in delight now can translate to exponential gains in 'free' advocacy later. #delight #utility #design

387

23 Comments

Does your software team speak the same language? Aligning on what basic UI elements are called is a great starting point. It doesn’t even matter what name your team chooses as long as everyone agrees on it. Names should hint at purpose. #productdesign #designsystems

60

3 Comments

When working with stakeholders on projects, a good question to start with is why the status quo isn't good enough. Stakeholders have a roadmap. They want to do something new, they want to improve something. Great! But can they clearly articulate why what currently exists isn't good enough and why we're getting ready to spend thousands of dollars to change it? From there, I'm often able to pull out more requirements and construct a narrative, build up the "why". 

4

Recently been looking at bunch of animation related stuffs (I think I don't like geometryReader). Trying to understand how #AppleInteligence enables smooth (maybe extra smooth?) morphing animation. Rough first step using Metal and few other tricks. #SwiftUI

32

2 Comments

Ngā mihi nui to all of the product designers who threw their hat in the ring for our recent round of hiring at Auror. We had 90 applications in total. We progressed 8 candidates through the whole flow, and 2 were offered positions. What set these two candidates apart was they showed us what made them different from the next designer. If you’re applying for design roles out there, here’s some tips from the hiring side: Go deep and flex your design skills when presenting work: The hiring team will expect you to know how to run high-level design process. That bit isn’t interesting, what is interesting is something unique that you bring to the table. Is it your ability to dissect a problem? Or extract a critical insight from customer research? Or break a complex challenge into deliverable solutions? Or make a room of C-Suite find their inner child? Show this off, talk about it in detail. The hiring team will think you’re super smart. Know your limits: We had a lot of intermediate designers applying for the senior role. While the adage of “shifting jobs is the easiest way to get a promotion” may be true in some scenarios, if you’re in a competitive recruitment process against people more senior, you’re on the back foot before you start. Apply for roles at your level (you’ll be a stronger candidate in that pool), then work on leveling up your job title. Please, please, please, get the business name correct: It seems obvious, but we had 6 candidates leave references to other businesses they’d applied to in their applications. Design is about details. It’s hard to claw your way back from a rookie mistake like this.

105

6 Comments

Why is content so hard? Over the last few days I've had several conversations about why organizations and teams over-invest in roles like visual or product designers or engineers all while under-resourcing content professionals and then expecting more and more out of them. It does not seem to be that organizations don't understand the value. I think by and large most people in business today would argue that content is important. Instead, I think it's an "everyone owns it so no one owns it" kind of problem. This great article by Michael Andrews isn't explicitly about this topic, but it helped crystalize something that's been knocking about in my head. (The article is really good, btw, so you should read it for what it's really about too 😀 ). But he points out that so many decisions about "content" made in an organization are often made by technical specialists who don't really care about what the content is about, who it's for, etc. To them, the content really is just another form of data to make technical decisions about regarding governance. This insight highlights what I think is the core problem. "Content" is more than just the presentation layer, more than the words or the images. Enterprise content is always part of vast ecosystem that in most organizations is broken up into discrete parts and then farmed out to different teams who often don't even realize that the part they have is even related to something bigger. It's like the old blind monks feeling the elephant problem. Today in most organizations, content is managed by a bunch of blind monks who have no idea that they're really managing an elephant. I think many content professionals see this bigger ecosystem and recognize the need for some kind of horizontal oversight of it, but by and large most organizations do not. #content #contentstrategy #uxcontentstrategy #contentengineering #ux #contentdesign

20

4 Comments

This is my 2nd Quest entry for Maigen Thomas's Quest Challenge. This Quest was Find and Fix a Deceptive Pattern; I chose Chipotle's platform on Uber Eats. I decided to focus on one specific user task, and the deceptive patterns in it. Maigen Thomas #MaigenUX #uxQuests #gamification #design #mentorship #MaigenThomas

2

Navigating Collaboration as a UXUI Designer in Collaborative Work Environments Hi Designers 👋 As a member of the collaboration-driven design team at TELUS Health, I’ve experienced the power of teamwork in breaking down barriers. In this article, I highlight the importance of collaboration and provide practical tips for junior designers transitioning from solo work to a team environment. Read more here: https://lnkd.in/euYhGQdf and let me know your thoughts! Thank you and Happy Designing 💻 #uxui #startup #design

3

I was using Perplexity.ai today and it was extremely helpful as always. The conversation was all about Android pixel densities and how am I supposed to handle different densities for images downloaded at runtime. I just wanted to make sure I display an image of only required resolution so that it loads fast on every device. At the end i asked perplexity.ai to write a blog about it and i have just published it. Here it is: https://lnkd.in/d8r5paUZ Yes it is mostly targetted towards engineers and managers of some mid tier companies because, I have never received 5 versions of every image from them. Here is my dumb conversation, in case anyone wants it: https://lnkd.in/d6jE_6QE #android #perplexityai #softwareengineering #perplexityai

13

1 Comment