César Rengifo’s Post

🚀 Exciting News from #Config2024: Figma’s Latest Features! I’m thrilled about the new features announced at the Config2024 event. Figma continues to lead with innovation and simplicity, making our design process even more efficient and collaborative. ✨ Seamless Integration: Now, we can create slides directly in Figma, making it a truly collaborative experience. 🎨 Flexible Design: With intuitive layouts and powerful design tools. 🔧 Innovative Tools: Game-changing additions like "Search for similar," "Make an image," and "Remove background" are optimizing workflows, boosting creativity, and improving productivity. 🚀 Simplicity and Efficiency: The new "Make designs" feature is set to revolutionize our daily workflow. Just describe what you want, and the AI creates it! #Innovation #Design #Figma #config2024 #Collaboration #Productivity

I am currently attending Figma Config 2024. Here is my virtual badge as I dive into two days of creativity and innovation. Excited to learn, connect and explore the latest tools and trends! #FigmaConfig2024 #Figma #VirtualEvent

🌟 Day 2 of Config 2024! 🌟 Today, I'm eager to explore more about design systems and dive deep into the latest features of Figma. Can't wait to see what insights and innovations the day brings!  🎨💡 #Config2024 #figma #DesignSystems #Innovation #TechConference

Here are the key points from Figma Config 2024: Introduction of Figma Slides: A new feature allowing users to create and collaborate on presentations directly within Figma. Launch of Dev Mode: Designed to streamline the collaboration between designers and developers, making the design-to-code process more efficient. Figma AI: Incorporation of artificial intelligence to automate routine tasks, provide design suggestions, and enhance overall workflow. Community Engagement: Over 75 speakers, 50 sessions, and 8,000+ attendees participated, highlighting a strong community focus. Innovative Presentations: Featured talks from industry leaders at companies like GitHub, Teenage Engineering, and The Browser Company, showcasing cutting-edge innovations and collaborations. Focus on Accessibility and Design Systems: Emphasis on creating robust design systems and ensuring accessible design practices. #config2024 #figma #figmaAI

Excited for the Figma config 2024! Can't wait to meet all the wonderful people from the industry and some exceptional talks. Few of the talks I am excited about are The Human algorithm, Crafting for the physical space, and Staying human in the age of distraction. Are you coming as well? Let's meet! #figmaconfig2024 #designconference

This screenshot is the agenda for Figma's 2024 Config closeout from 7:30-8:30P. Does that last session with Jason Ballard really say what I think it says? #RewirewithAI #futureHuman #buildingHumans #buildingHumansinFigma

After watching the interview of Lenny with Claire Vo and Dylan Field , now I have the answer for the triangle quiz between: Scope of Work, Quality, Timing in building product. I learnt that if we can adjust some aspects, it will be Scope of Work first, narrow down scope of work for Minimum Viable Product / Feature. Then we can set the quality bar to minimum but acceptable, to build the product as fast as possible and gaining feedbacks from users, then iterate it and improve it on next sprints. Let me try this approach with Leveling app 😎😎 Thank you!

Speed is a key. Yet quality has not to be overlooked. Building features fast is important, yet set a minimum quality bar to release, then raise the bar with continuous improvements. After shipping and receiving feedback, balance between building more features and enhancing the quality of what you shipped.

At about the :40 second mark, Dylan Field talks about "quality, features, and deadline...choose 2" when it comes to product releases. And 9 times out of 10, I'm going to choose quality and deadline like he did. It doesn't matter if it's a massive product launch to millions of users or a v2 of an existing product for your 100 B2B customers. A new product release needs to look like it went through some sort of quality check. No typos, no error messages, no graphics that aren’t loading. Call it the broken windows theory but those basics are needed to show you've put thought and care into what your users will be interacting with. It will show the product has been tested and that you've knocked out the most egregious bugs. And the deadline is a tactic I will frequently use with engineering and product teams. (We used it back in December when launching Stacker's customer-facing analytics portal.) Pick an arbitrary date. But that arbitrary date should be: 1. Soon enough to make the team feel just slightly uncomfortable...but don't freak them out. You don’t want teams operating in fear or working around the clock. That's when mistakes get made. But just like trying to shave 30 seconds off your mile, it should be ambitious. 2. Any day other than Friday. Initital launches often have mistakes. No one wants to be triaging bugs and deciding whether to rollback the deployment at 3pm on a Friday afternoon. 3. A day most people will be in the office. Check calendars in advance and avoid dates when key members of the team will be on PTO. And most importantly, CELEBRATE the win and give the product team a little bit of breathing room. Don’t start brainstorming the next feature release 12hrs later. (But maybe after 48hrs 😉 )

Here's my virtual Figma #config2024 badge. It's fascinating to see how design systems can unlock new levels of creativity. Gearing up for Day 2! #config2024 #figma #productdesign