Masterclass Summary:
In this Supercharged! Masterclass Jordan dives into the basics of how data is structured in Podio. It’s a simple episode, but it’s a critical one. Understanding how data is structured in Podio will help you make decisions on your system design.
In this masterclass you’ll learn:
- The basic structure of Podio: Organisation – Workspace – App – Item
- The importance of structuring your apps inside of relevant workspaces
- How to navigate to your workspaces and apps
Transcript
Narrator 0:01
You’re watching another supercharged masterclass with Jordan Samuel Fleming your opportunity to learn the ins and outs of Podio design and development from one of the top Podio partners in the world.
Jordan Fleming 0:14
Hey, everybody, it’s Jordan Fleming here with another supercharged masterclass. And today, I’m going to dive into the basic Podio data structure. So this video is really going to about helping you understand how polios data is structured, so that you can have a better understanding of really how to build Podio, effectively using that structure, how you’re going to take what you do in your business on a day to day basis, and bring it into Podio. So we’re going to dive into that, I’m going to show you a bit about the structure and talk a few best practices around that as well. Let’s take a look. Let’s talk about how polio data is structured. I’ve drawn this out here, just to give you a sort of visual idea around this, essentially, polio from the top down starts at the polio organisation. And that’s usually if you’re not the person who owns the company, then it’s usually been set up for you, you get invited into an organisation and the organisation. Underneath that you can have multiple workspaces. So you can have really as many workspaces you want, although too many workspaces can lead to clutter and confusion. So you know, you gotta be careful about that. And Workspaces are really there to be a collection of apps. And it’s the Podio apps that are where the power because Podio apps is, you know, it’s it’s how you lay out fields and decide, you know, what data you’re actually going to be capturing. And of course, inside of the apps are your Podio items, this is the actual data that you are working on the data that you are capturing. I used to train them this when I used to introduce Podio to people into inside of organisations. And when put your training days, I used to sort of liken it to Podio being being like a house. So if you think about Podio is a house the Podio organisation is your house. Hey, are you using Podio to manage your real estate investment business? Well, click the link to find out why 1000s of real estate investment professionals are using Podio plus smartphone to make more calls, send more text and close more deals, click the link. inside your house you have many rooms, multiple rooms. And those are equating to your workspaces. And inside of each of those rooms, you have apps you have what I used to call is file cabinets. And inside of each file cabinet, you have a set of files and those are your items. Right so your house has got lots of rooms inside of each room has a lot of file cabinets and inside of each file cabinet, you have a lot of files. Now this kind of goes to one of the other principles of Podio design, in my opinion, which is collecting apps inside of workspaces. So I will see a lot of times particularly for new people who are building Podio for the first couple times I will see them build out a tonne of apps in one workspace. And I think that is a really bad practice it leads to really terrible onboarding processes because you end up having 50 apps in a workspace and you’re having to you know sort of train people on everything and be like oh ignore these 20 and only work on these five and and if you think about polio as an a house, you know, you we collect things inside of our houses into rooms that have functions so you know our kitchen is where our stove and our oven and our you know fridge freezer our and our sink, you know that it’s where our food is we collected there because the function of that room is to be a kitchen, the same as a bathroom same as a bedroom, etc. We have functional uses to most of our rooms. And the same is true about Podio workspaces in my opinion. You should have functional reasons to have a workspace. Okay, hands up who’s using Podio for real estate and they don’t want more Leads. Nobody. You want more Leads closed well check out smartphone for Podio the only phone system fully built for Citrix Podio with an fully integrated power dialer and amazing mobile apps. It means wherever you are, you can make more calls, love to Podio send more texts, love to Podio and close more deals, all logged to your Podio CRM, click the link. Check it out. And I’ll show you some examples of that. So let’s pop into Podio.
Again, if you can’t remember your workspace and organisations are up here on the top left hand corner, and do remember that you can search But here’s an example of exactly what I just talked about. A certain force here in this case is the organisation. It’s the house. And then we have a collection of rooms, we’ve got a collection of workspaces. And you can see that they are numbered and named as such to group them into functionality areas. So we’ve got CRM, we’ve got wholesale Transaction Manager, all sales system configuration, inbound data, cold calling lists, format, or track commissions record, those are functional areas, much like a kitchen is a functional room in your house. And if we look at one of those functional areas, we will see a set of apps, these are the apps we’ve built that work within this functional area, in this case, contact companies, emails and communication that smartphones app to track our calls, and text messages, voicemails, et cetera. Inside of each of these apps is of course, our data. We’ll click on it, we can see we have 903 items, either in C files in this file cabinet. 903 bits of data that if I open up, I can go ahead and look at are using Podio. With call rail. There’s a better way, click the link find out why hundreds of businesses have moved over to using smartphone, the only phone system built for Podio. Make more calls, send more texts and close more deals, click link all of the bits of data that are around this one item inside this one app. So again, your organisation has a bunch of workspaces, those should be functional, but should be grouped as functional workspaces like rooms. Inside of each functional workspace, you have a collection of apps, those apps are what your business processes are built off of. Where what type of information are we storing here? What processes are we working on? What are we doing in here, they’re laid out in apps. And then of course, your actual data are laid out as items inside of those apps. And it’s really important that you think of these things as functional areas, because otherwise it’ll lead to a lot of clutter. nothing I hate more than seeing a workspace with a lot of people working in it on a day to day basis and there being 35 apps. It just all it means is things are hidden away. They can’t see them. It’s hard to train people. There’s a bunch of things they don’t need that to wade through. It is just bad design, practice. So disagree. Agree. Hit me up on the YouTube video. Drop in a comment. If you want anything for me to talk about the future. You want to disagree. You want to talk about any issues that I’ve raised in this video. Just drop it into one of the comments. Please do hit subscribe, make sure you’re notified of any other videos. And of course, subscribe to the podcast on Apple podcasts, Google podcasts, Spotify, wherever you get your podcasts. Make sure you like give us a review, give us a share, the more we can spread the gospel of Podio the better. Thanks very much.
Narrator 8:10
Thanks for watching this Supercharged masterclass with Jordan Samuel Fleming CEO of smart bone don’t forget to hit the subscribe button on our YouTube channel to be notified of new podcast episodes Podio masterclasses and in depth Podio extension reviews
Add comment