What inspired you to start the 'A Tip a Day' project, and how did the partnership with Autodesk Big Room come about?
This all started as a wild idea one night. I was frustrated, digging around for small fixes and little tricks to solve problems in Autodesk software. I kept thinking, why is it so hard to find these simple things that can actually make a huge difference in your day? That’s when the idea hit: what if we shared one practical, bite-sized tip every day, something you can grab and go with right away.
I mentioned it in passing to the team at Autodesk Big Room, and with their encouragement, I took the leap. That’s how A Tip a Day was born. Now, every single day of 2025, a tip goes out, sometimes from me, sometimes from contributors. Nothing long or complicated, just quick insights designed to give someone that little boost in their workflow. There’s also a monthly newsletter available only through Big Room that brings everything together in one place. You can access the newsletter through the Big Room at https://infl.tv/otHv.
Why do you think community-driven knowledge sharing is so powerful, especially in the AEC industry?
There’s so much knowledge in this industry. Some of it has been built up and refined over years, and some of it is brand new as technology keeps evolving. Both types of knowledge are valuable. The pace of change is intense right now with new tools, workflows, and expectations showing up all the time. If we each try to figure it all out on our own, we’ll always be behind.
Communities are where those connections happen. Sometimes the best tips come from the most unexpected places. It might be a seasoned pro sharing something they’ve relied on for years, or someone new spotting a shortcut no one noticed. Even the smallest tip can shift the way a team works. That mix of experience and fresh eyes is what keeps things interesting and keeps us all moving forward.
How does the ‘A Tip a Day’ project help strengthen the sense of connection within the global AEC community?
The thing I love most about A Tip a Day is that it’s “no obligation” knowledge. You don’t owe anyone anything. Take the bite-sized tips that help you, leave the ones that don’t, and pass along the ones that might help someone else. It’s really that simple.
There’s no gatekeeping here. Sometimes we treat expertise like a currency you have to protect. I don’t believe in that. If a feature, trick, or shortcut can save you ten minutes today, it can save someone else ten minutes tomorrow. Multiply that across a community, and suddenly you’ve got hours, days, or even weeks saved. This project is about building a culture where knowledge flows freely because at the end of the day, we all depend on these tools to do the work we’re passionate about.
What role do you see communities like Big Room playing in the future of industry innovation and collaboration?
Big Room has been the perfect home for this project. It’s not just another forum or a place to drop technical questions. They host meetups where you can actually talk face to face, run challenges that get people thinking differently, and even throw in games to keep things light. It’s the kind of space that makes you want to come back, not because you have to, but because you feel connected.
The real magic is the people behind it. Alex, Sam, and Bri are the heartbeat of Big Room. They’re not just moderators or organizers, they’re facilitators who genuinely care about building relationships in this industry. They highlight individuals and celebrate more than just what comes out of the software. That spirit made Big Room the natural fit for A Tip a Day, and their encouragement gave me the push I needed to make it happen.
If you want to join the Big Room community, you can sign up at https://infl.tv/otHv.
You can also join the LinkedIn group for ongoing discussions at https://www.linkedin.com/groups/13126825/.
How do you ensure a consistent flow of daily tips for 365 days? Is there a team or system behind the scenes?
People ask me all the time how I manage a new tip every single day. The truth? There isn’t a big team working behind the curtain. It’s me, figuring it out as I go, with a huge boost from contributors who step in to share their knowledge. The Autodesk Expert Elite community in particular has been amazing. They’ve been my most consistent supporters and have shown how much value comes from simply sharing what you know.
On a practical level, I try to stay ahead when I can. If I know I’ll be traveling, I schedule tips in advance. Sometimes I’ve got a backlog, and other times I’m putting the day’s tip together in real time. The only real structure is the project template we created so every post looks consistent and recognizable. Beyond that, it’s the community’s energy and commitment that keep the project moving.
What criteria do you use when selecting or curating the tips submitted by the community?
Anyone can contribute, as long as it’s Autodesk-related, works, and fits the template. If something needs editing or clarification, I work directly with the contributor to get it right. I love seeing the creative ideas and solutions that come in. People have a lot of knowledge to share, and as long as it’s accurate, it belongs here.
How do you ensure that underrepresented voices or smaller contributors in the community also feel heard and valued in this project?
Every contributor is treated the same. Whether you’ve shared one tip or twenty, your contribution is recognized. All tips go into the monthly newsletter, so everyone gets visibility. I only step in to fill gaps when necessary, but this is a community-driven project first and foremost. If you have a tip to share, there’s a place and a platform for you.
What has the response been like from the AEC community so far? Are there any success stories or milestones you’d like to share?
Honestly, the response has been amazing. People message me to say a tip saved them hours, or they share it with their team. Sometimes someone will try a tip and then send me a new one they discovered, continuing the cycle of shared knowledge. It’s never been about reach for me; it’s about small wins. Even one person learning something that makes their day easier is a success.
What has been the most rewarding part of leading this initiative for you personally?
The monthly newsletter is hands down my favorite part. It gives me a chance to reflect on what’s been shared, highlight contributors, and see the project take shape day by day. Watching it grow, tip by tip, has been incredibly rewarding.
What are your hopes for the future of this project beyond the initial 365 days? Could this evolve into something bigger?
The project won’t just end after 365 days. In 2026, it will evolve. The newsletter is here to stay, but I’d also like to see it grow into more community-driven initiatives: maybe monthly roundtables, topic-based meetups, or whatever the community decides they need. The key is listening to the community and letting the project grow to serve them best.
Conclusion
This project isn’t for me, it’s for anyone who needs it, whenever they need it. The knowledge is here, easy to find, and always available. Download the tips you like and make a booklet. Grab your ten favorites and share them at work. You never know when something small will make a big difference. And if you’ve got an idea you want to share, there’s space here for that too. Together we are stronger.
I would like to thank my contributors:
Arshdeep Singh, Arthur Knoors, Christian Fierro, Chukwuebuka Stephen Idafum, Dzan Ta, Frank Mayfield, Gil Cordle, Mark Jung, Matt Flanders, Shelby L. Smith, Tom Richardson
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.