Design Decisions #2: Redesigning Adminland

[@adammiribyan674]

This is gold. Loved the “non-admin users being able to see what admins can do” part and the reasoning that supports it.

[@gettingreal8980]

Thanks! It was a new idea we tried in 3, and we still feel great about it. -JF

[@koviniskaciukas]

Loved it too. I'm a software engineer and I've seen lots of products where admin section is not even accessible if you don't have the rights. This is really interesting take and very helpful for me as I bootstrap my own product.

[@UsefulProgrammer]

This is great. I really like the philosophy of telling non-admins what the admins are capable of. It's something I never thought of before, but when you bring it up, it's a 'no duh' moment. WordPress would benefit from implementing this.

[@dixpac]

Great content :)...Love how you folks are introducing these changes gradually so people can adapt (well if we exclude direct messages attempt :)). When I think about the first version of Basecamp 3 a lot has change since then...Thank you!

[@tejaskumthekar4155]

This makes a lot of sense. I've experienced people pinging on slack channels to ask who can do what. Having a dedicated aggregation for this stuff is a great way of maximising autonomy in teams and minimising context switches.

[@Merrycreation]

While I like this design decisions episodes, I would love to see episodes on how do you use Basecamp internally. We can have a glance at it during the last two episodes but it would be great to have something only about it. We use Basecamp in my company and sometimes we struggle to find a good way to do so stuff. We try, we fall, we refactor, we find something that work, rince and repeat. It would be a real time saver to see experienced users sharing their ways to use Basecamp. For instance : how do you handle onboarding. Marketing campaign. New design cycle. New backend dev cycle. Management (remote people or not). How do you (as a CEO) read through Basecamp ? Do you read all daily check-ins ? What is the check-in policy at basecamp ? Is it mandatory to put a daily answer ? What if you don't hear about something for several days in a row ? Thanks to you and David to doing these episodes.

[@jf4841]

Franck D'agostini got some of those coming up. Stay tuned.

[@SchalkNeethling]

Love this, this is a brilliant idea. Thanks for sharing Jason

[@shivamdaryanani3204]

Nice, thanks for this. Would love to see more in depth discussion of the design process itself.

[@sevab3704]

Really love these series, thank you for sharing!

[@HarvestProfit]

I love these videos. Thank you.

[@pruettsk]

Good stuff, Jason. I wasn't aware that non-admins could see Adminland, but how BC does it makes a lot of sense. One thought: for consistency and clarity, it might be worth considering changing "Nudge an admin/account owner" to "Ping an admin/account owner."

[@gettingreal8980]

Yeah, agree. Nudge isn't language we use in the app, so Ping would make more sense. -JF

[@santosharjun]

Thank you!

[@usemylink5017]

Future design decisions episode idea: giving confidence to someone during (before?) what can be considered an anxious action e.g. I just commented something I only expect these people to see, or I just archived a project how does this impact others?