Transcripts
1. Introduction: Thank you so much for taking class number three. This is Beyond Excel 3, applying Coda to real life scenarios. If you haven't already please take classes number 1 and 2 in the bionic sell series. It will give you a really good foundation, for the productivity tools in the workplace with a specific focus on Coda, a productivity tool we've been using throughout all three classes. In this class, we're going to focus on the most popular templates used by everyone from independent consultants all the way up to [inaudible] companies such as Uber. Keep in mind that these templates are strictly just templates. So many users and companies end up changing the data to fit their needs and scenarios. We'll walk through that in the various lessons. A key aspect to all coda docs and templates is that they're very collaborative. So keep that in mind when you're thinking about building your doc for your team. Because you want to be able to invite your team to use your docs and your templates. We're going to be going through three different templates, a beginner, intermediate, and advanced template. So we're going to talk about docs for doing a personal CRM to what to do list, and all the way up to a cross-functional project management doc you can use for managing projects with your team. There are additional templates you can look at on the Coda website at coda.io/templates. There should be a link to that in the class notes below. So I look forward to seeing you in lesson 1. If you have any questions, feel free to leave a comment in the [inaudible] section below, and I look forward to seeing you in the future lessons.
2. Personal CRM: Tracking for Entrepreneurs and Business Owners: Welcome to lesson 2, personal CRM tracking for entrepreneurs and business owners. In this lesson, we're going to look at our first template in coda called a personal CRM. This CRM doc does one thing really well, which is helps you keep track of people that you talk to in a worker interpersonal life, and also the interactions that you've had with these people. If you're working on a small sales team sometimes HubSpot might be overkill for what you need, so this CRM tool will help get the job done for you. I built similar CRM tools in Google Sheets, which I'll show you in this lesson. But hopefully this CRM tool will be very useful for your daily work or personal life. In this lesson 2, we're going to look at a template that is used by a lot of independent freelancers and consultants called the Personal CRM. The first thing I want you to do is make sure you have a copy of the template available. The best way is probably to click right here on this link to go to the coda website. Once you go there, you'll see a personal CRM template that is just a preview. But if you click on Copy Doc, it will give you the template which looks like this in coda. Please go ahead and make sure you have this doc open so that we can get started with this lesson. The reason why we're starting with this template is, this template is relatively simple to use. We're going to go through this in the next few lessons. But keep in mind that sometimes if you're working on a sales team where you needed track sales and deals, but you aren't that big of a team yet. Using a tool like HubSpot or Salesforce is way too complicated to the CRM. There much easier ways to keep track of people you're talking to, their companies, what your meeting notes interactions are with them. That's why we're going to discuss a personal CRM as the very first template that's used by a lot of independent consultants and freelancers as they're building out their business. All this template is, it's just a quick way to keep track of people you meet in life and in business and just to keep track of the things that you guys talk about on your day-to-day meetings. I actually tried building something like this, a personal CRM in Google sheets before. It got really complicated, so I ended up just using the personal CRM template and coda. But to give you an idea of how complicated things can be if you're building a CRM that's not in Salesforce and not in HubSpot and it's way too much overkill and you want to build something more for yourself. It can still get pretty complicated Google sheets. This is an example of what a CRM looks like in Google sheets. When I was freelancing, I did something similar to this where you have a CRM report and this is a huge CRM template. Actually, we're not going to look at something as complicated as this, but you have a tab for just your people and other details and companies and opportunities and all of these various setting so it can get pretty complicated. I mean, this is usable, but if you don't need all this detail and you don't need all these complicated sheets linking together to build a dashboard, a simple CRM built-in coda this personal one is all you will need. For all you consultants and freelancers, entrepreneurs out there, hopefully this template will be useful for you and move onto the next lesson as we discuss how to actually start using this template for your own needs.
3. Personal CRM: Logging People & Interactions: Welcome to this lesson. Lesson 3, Personal CRM: Logging People and Interactions. In this lesson, we're going to continue using our personal CRM template, and actually start adding people and interactions to the template, and to ultimately build a database for our CRM. Welcome to Lesson 3. Now we're still going to be using the personal CRM template, that I showed you in Lesson 2. If you haven't already, please make a copy of it, so that you have this template open. Let's try to add a person, to the people table in the template. Again, all this tool is a simple way to keep track of people you're meeting with, and also the interactions that you have with them. Let's start logging some data. This is something you can actually use for yourself, if you want to start using this for your personal life or for your work, as you're meeting with business and clients. I'm going to add a row here. Let's say I recently met with Ronald. Actually, let's use an example that I always like to use. Let's say you've recently met with Zack Morris form my favorite TV shows. You notice how like this full name automatically just added these two words together, because uses the concatenate formula. Let's say I know Zack from my hometown, technically I watched Several developed when I was growing up as a kid, in my hometown. This is actually built off of the interactions table, which we'll talk about in a bit. This interacting topic is also built off of the last interactions tables. We won't actually fill these out for now, but let's say I want to keep track of other details about Zack. Let's say his spouse's Kelly Kapowski and they have kids, I don't know if they had kids in the show, but let's say they had a kid named Tim. Now I added my own person to the people table. Now let's add some data to the interaction table. To keep track of what things exactly Zack and I talked about last time we met. Here's the interaction table, and I want you to add to the very bottom. This is all again dummy data, you can feel free delete this if you want to. But over here, you can now log details about what you guys talked about. Let's go down here. If you notice, this is actually a lookup to the people table. Now if I click on this drop down, it will show me that Zack's name is at the very bottom, and all these other names show up in the people table here as well. You notice how the full name is the display column. That's actually what shows up in the drop-down menu here. The full name, not the first name or last name, but the full name. I'm going to click on Zack Morris here. Let's say the last time I met him was, a call, the date was, let say June six. Let's talk about a few things that we talked about. Bullet point, let's say we talked, Zack mentioned Mr. Bedling is getting annoying. If I want to insert any ballpoint I can hit on the "Mac", you hit hold the option key, and then hit "Enter" answers and you ballpoint. On the PC, you hit "Control" and then enter key. Let's say he also mentioned that Screech is planning to ask Lisa to the dance. Those are just two things that Zack and I talked about in our last call. If I go back to the people table, you notice that these two things automatically failed out right here. My last interaction date was 6-6 and my last interaction topic was those two things I just wrote about. If I were to add another interaction, let's say I talked to Zack again. This time I made an in-person meeting and we, let's say talked about Slater's new workout. Let's see what happens when I go back to the people [inaudible]. I still have just these two rows of data, where I had interaction with Zack. If you go back to people, you notice that it's still only has one row for Zack, but if I scroll over to the right, actually let's change this date to 6-8. Now the Slater comment about the workout is the most recent interaction. They go to people. You notice that it only selects the first interaction topic, that I had with less interaction topic. This formula is supposed to take the last topic that we talked about for Zack. In theory, this was supposed to change, but it looks like the formula might not be working, but not to worry, we can fix that in, maybe if I can change call maybe that might work. None of them seem to make it work, but regardless, this in theory will show you the last topic that you guys talked about and I can fix this template for you, if you just give me a shout, but this will in theory, show you the last topic that you talked about with that given contact. Very simple way to add people and interactions to your table and then they all can link up together, so that you know who you talk to and what you guys talk about. Thank you for watching this lesson. Move on to the next one, as we talk about, how do you figure out who to reach out to in this basic CRM tool?
4. Personal CRM: Viewing Who To Outreach To: Welcome to Lesson 4, Personal CRM: Viewing Who To Reach Out To. In this lesson, we're going to continue using our personal CRM template and viewing who we should contact and reach out to looking at our contacts as Trello cards. We'll also explore using formulas in the Canvas to summarize our CRM data. Please follow along this lesson. Again, if you haven't already, please make sure you have a copy of the template. It looks like this. There's only three sections in the template. You'll notice that in the last lesson, we added a person to our table. We also added an interaction and I figured out why, you notice how Zack Morris right here, we logged a role here for our meeting with Zack and then up here was our next call where we talk about Slater's new workout. If you go to people, now shows Slater's new workout as the last interaction topic. But if I were to move this interaction with Zack where I involved that talk about slater below or called Zack, now, the last interaction becomes those two bullet points where we're talking of Mr. Belding. That's because it just looks at the interactions table and takes the first row where it matches up with Zack's name. Anyways, if you look at the view or either the section for need to contact, you can see now this is basically our data, but it's laid out on Trello cards before it was table. Right now, we can actually just look at this as Trello cards. You can actually move these people between the different lists. Let's say Dwayne Johnson actually was someone from work. You can move that from work to home town, and it all changes with the underlying data right here. Let's see, that person was Dwayne, so now Dwayne should be from hometown. Before, Dwayne was with the college. Dwayne now is from college. This is a nice handy way to see who's your contact and it creates a nice view of all different people. What's cool is if you click on this little icon right here within the Trello card, it launches the row detail where you can see all the fields associated with that given contact. Ted Smith had less interaction topic and also their kids and spouse. This is a nice handy way. This card gives you nice summary view of all the data of that given person but the row detail gives you all the detail you need to be able to see things that you can't see from the card. While this is an interesting view for Trello, I'll tell you why this Coda Trello view is a little better than this regular Trello. If you were to see a CRM pipeline tool in Trello, this is an example of what it looks like. I put a link in the doc right here, you click on it and check it out. This is a full fledged CRM tool in Trello. Notice how you have contacted leads, all that meeting scheduled but the problem is that you can't really keep track of deal amounts or deal sizes and $ signs, because this is really meant for texts. If you wanted to keep track of like $ amounts for this person or have specific fields for the contact information, you can't really do that in Trello. You probably have seen this before if you've used Trello before where you have a CRM. But with Coda, you can put all fields here, including the date, obviously tax, you can also include numbers like how much, let's say you want to attach a certain deal amount for this given person or a given sale amount for this given business contact. That's where Coda can become more flexible because imagine your Trello CRM being able to be visualized like this, but you can also convert it into a table format where you can see all your data, like you would in Excel, where I can remove this group right here so that it looks more like a table. That's why seeing your data as Trello cards can be much more flexible compared to just regular Trello. As you're viewing these contacts, you can obviously change their details, like changes to hometown and guess what? That data will show up and will move here. Same thing with this guy, let's say I want to change from hometown to college, that card moves to college. Hopefully, you can see how flexible Trello card view is with your regular table view. Also you can see up here there's a basic formula for the number of people that I've interacted with in the last 30 days. Those two people are just the two times I spoke to Zack Morris. If you remember, from the last lesson, you can see how you can use formulas to quickly show the people you've contacted in the last 30 days. This is using a simple formula using the interactions table, plying a filter, and then counting the number of times that those rows match that filter. Hopefully you've found this personal CRM tool useful. Start using it for your own personal or work-life and let me know of any questions or comments in the class notes community below. We'll go to a little more intermediate template where we're going to look at a to-do list. Please follow along.
5. Getting Things Done: GTD with David Allen: Welcome to lesson 5. Getting Things Done, GTD with David Allen. You may be familiar with David Allen. He has a framework called Getting Things Done and we're going to explore a Coda doc built on the principles of Getting Things Done. Please follow on this class lesson and I look forward to hearing your comments. In lesson 5, we're going to start with a brand new template called Getting Things Done, GTD with David Allen and if you haven't already, please make a copy of the template here. The easy way is probably to click on this link right here and you'll see a preview of the GTD to-do list template over here and hit Copy Doc and you'll have a Doc that looks like this to get it open. The reason why I like this template specifically is because it's based on David Allen's own framework for Getting Things Done. You may be familiar with this framework. Here is his website, gettingthingsdone.com appropriately named. It starts with five steps; capture, clarify, organize, reflect and engage. We're going to take his simple steps here and apply them to the template and so if you have a to-do list or you have a way of tracking things you need to get done on a day-to-day basis, we like to use the David Allen's framework of GTD, Getting Things Done and we're going to use this now in the template. Please go to the next lesson as we start filling out our own to-do lists using this framework. Looking forward to seeing you in the next lesson.
6. GTD: Capturing & Organizing: Welcome to lesson 6; getting things done, capturing and organizing. We're going to continue using the getting things done template we went through in the last lesson, based on David Allen's framework, and we're going to start adding data, to adding things to our to-do list, and also using formulas to capture when those to-do items are due. We'll also look at building multiple views off of a single table, so please follow along in this lesson. If you haven't already, please make sure you have a copy of the getting things done templates, it's a to-do list template, and it's based on David Allen's framework of getting things done. It looks like this. We're going to start to add a to-do item to the capture table. As you know, the first thing you have to do with David Allen's framework is to capture all the things you have to do into a central repository. If you go to the template, the first pages is just an intro to the doc. But if you go to the capture section and click on "Capture", you notice that this is where you start basically keeping track of all the things that you have to do. We already have a few things pre-filled for you right here. But I want you to start writing in a few tasks for yourselves. I'm going to start writing one right here. I'm going to say, plan next Skillshare class, priority, let's call it medium. The project is a drop-down. This is a look-up from another table called projects, which is right here, which we'll look at in a future lesson. But for now, just pick one of these projects for now, I'm going to call this a personal project. Let's give this a due date of, let's say a month from now. Today's June 6th, let's say July 6th. You notice that in the template, you have the ability to remind yourself of when you want to be reminded about this task. You can actually move this slider, which is another column type of this column type slider right here. This is using another advanced formula called switchIf. This lets you basically add in really interesting icons if you want. But most people usually use this for text, so that you can see when the due date is for this task, and this task is due later, that's why there's this later text. This column is also for when the reminder is going to happen. You can also check off if the to-do task is done, you can clean it off right here. But for now, we're going to leave this as a date. This is going to remind us on July 21st to do this task. If it's done, you can go check it off and you get this nice little happy face. That's how you can capture all the things you have to do, and you assign them a priority, and also give a project or category. We'll talk more about how this flows into the remaining of this template in future lessons. On the Organize section, this is second part of the framework for David Allen's. Once you've captured everything you have to do, now you can start organizing and putting things where they need to be. This is essentially a view off of the capture sections. If you click on this link, you notice that organize is just like a child of the capture table. We've basically grouped everything by priority. Everything is group from high, medium to low. Let's see what's next on the to-do list here. Actually we viewed some of the formulas in the capture table. Let's actually look at some of the hidden columns in the organize table. These are all just the same data you'll see in the capture table, but there's some data that's been hidden. There's only 1, 2, 3, 4, 5, 6 columns here. But in the capture table, there's many, many different columns, more than six. Here's where hiding columns can make things a lot more organized for your table. That's why this section is called organized. If you click on this eyeball here, we've hidden Done, and the reminder dates, and the category. We can also hide things, like next action to make the table even cleaner. But the next action definitely helps us with knowing what the next steps are for that given task. Let's keep that in there. But hopefully this can show you how, once you've captured all your to-do list or tasks in this table, now you can start organizing them by party or by project, and then you can start hiding columns to only see the data that makes the most sense for you, and is of the most important for getting things done. Hopefully you found this lesson useful for capturing and organizing your tasks. In the next lesson we're going to talk more about viewing the actual task you need to do, so follow along for the next lesson.
7. GTD: Custom Views of Your Tasks: Welcome to lesson 7, getting things done, custom views of your data. We're going to wrap up our work with the getting things done template, and we're going to look at constructing the views off of the table, but also how we can better clean up our views so that it's much more easily readable for our users. Please follow along in it's lesson. In lesson 7, we're going to keep on building half of the GTD, getting things done to-do list template. Again, if you haven't seen a template or copy the template yet, please do so, it looks just like this. But we're going to build off of this template some more and look at the specific views of our to-do lists within this template, we're also going to look at the projects table a little more depth to see some formulas built in there. But ultimately, my goal for the takeaway from this class is that you can see your tasks table and many different ways depending on what's important for you. If you go back to the template we went through capturing your to-do lists, I added it to do of planning my next Gaucher class, we can organize our to-dos. So my sculpture class ends up in the medium priority, and I don't have a next action item written for this one yet, but here are all the views that are really important for you in terms of how you want to view your to do list. If I look at today, these are all the tasks that are past due, they're from long time ago, but if you look at the filter for this view, again, this is a view because if you click on this little link here, today is just like a child of the capture table, and the capture table is right here. This is like our main master table with all our data. Let's go back to table today. This view is filtered by any task that is not done, that's why we have done equals false, and when the when column equals today. Let's go back to the main capture table again and look at what that means. You'll see that some tasks are not done, some are done. But the when column also shows, is this a task that's due today or is it due later? By default, anything that is past due is going to be due today, because something that was supposed to be done in the past. You notice that this filter basically takes all the tests that are not done and we do in before. This might be an important view for you to look at, to see what are the most immediate tasks that are late and delayed, and you have to get done as soon as possible. Upcoming is if another filter, it's looking at anything that's done equals false, so things are not done as well but their upcoming. Since there are no tasks that are upcoming, this there's nothing that shows up here later, these are all tasks that are due. Let's look at the filter right here, again, tasks that are not done, but they have a later value. Again, you notice how my skills your class wasn't they always do later. If I click on this checkbox, this sculpture class will be removed from this view of my main table. Let's see what happens when I click on this thing right here. You notice how it disappeared after a few seconds, so now I can only look at the things that are due later. There are some of the more additional views here someday and logbook. These are additional views, these are probably for tacit or do way in the future, so we don't have to look at these now. You can actually view task-based on this date, but we're actually not going to look at this for now. But this is also one way to look at your task is by picking specific due dates and you'll notice all the tasks here. The last thing I want you to look at for this lesson, let's go back to our lesson plan here, is looking at the formula and the project table for tasks, also we're going to try grouping by project instead of by category. What's interesting is that if you notice, this is also again a view of our main, this is actually a new table called projects, and it's actually like a summary table of all our tasks. What does that mean? If you look these tasks right here, these are actually formulas that are built off of the organized view. When you build out formulas, they don't have to be built off a table that could also be built off of views. This is actually looking at all the tasks associated with the offsite project, and it's putting into a bulleted list. What does that mean? Let's look at product specs and within our organized table. So product specs are these two guys right here, follow-up doc organization and figure out a new approach to on boarding. They show up as bullet points here because we added the bulleted list action at the end of our formula. If I delete this, it just get rid of the bullet points and is not as nicely formatted. But this is a nice view to quickly see for all your given projects, what are the tasks that you have to do next to complete it. This also gets grouped into category. If I remove this group, on group column, you notice how it just duplicates that multiple times, so it's not as useful. Now, what if you try grouping by project? Let's see what happens if I do that. Group along left, you notice that it's not super helpful because project was already like a unique value within project, we already had a unique values. This is not that useful because and you can see work is here, work is there. But if for some reason you want to add additional rows, the build tools section, build tools group you can add right there, and you can just say, I want something to do with work and add all this stuff, but this is this one pull any data because we don't have anything related to build tools and work in our main table. Let's just remove this group and go back to grouping the category. Hopefully, this will give you a nice overview all your to-do list items and also give you a progress report of how far along you are. This is also another formula too. If you have any questions about this template, feel free to reach out to me, my e-mail is right up at the top of the lesson plan here. You can also ask us questions on the question mark. But hopefully, this is a great template for your use as you're planning your to-do lists and figuring out what to do next. Hopefully I'll see you after the next lesson where we go through a much more advanced template called a product launch hub.
8. Launching Your Product: The Hub: Welcome to Lesson 8, Launching Your Product, The Hub. In this lesson we're going to look at a cross-functional project management template, and we're going to look at how it's laid out, as well as how we can capture everything from tasks all the way to creating a wiki and also capturing meeting notes all in one single template. Please follow along with me in this lesson and I look forward to hearing your questions. Now whether you're launching a small feature or working on a large cross-functional project with many different teammates, this template that we're going to review on Lesson 8 is the most popular template used by independent consultants all the way up to large companies such as Uber, who use it to launch one of their most popular driver applications. Make sure that you have a copy of the Product Launch Hub template. You can go to this link right here, and this will give you a preview of the Product Launch Hub. Then you can just hit "Copy Doc" right here, and it will give you a copy of this template to put into your Google Drive. We're going to quickly look at the first section of this template, and just to keep in mind how this template is structured. You can see there is many different folders and sections. Now, the way this template works actually goes back to what we discussed in Class 1, if you took Class 1 already. In Class 1, we talked about different document and communication of workflows where you are constantly copy and pasting from Google Docs into Google Sheets, into other tools like Trello and Asana. This template eliminates all that copy and pasting because you can keep track of meeting notes, you can keep track of a Wiki, you can keep track of tasks all in one place. For instance, like here you have just regular text, here you have a spreadsheet-like interface, and then here is just keeping track of meeting notes. This is how powerful Coda can be for project management, is that all these various formats can be put into one central doc, so you're not copy and pasting things from Trello into sheets or Google Docs into Google slides, it's all one single source of truth. We've got some mix of text, you have a wiki, and also a mini tracker all on one place. Of course, you could use dedicated project management tools like Asana or Basecamp, which you could be using today. But there are certain times when you might have a specific feature that you want to have in Basecamp or Asana but it is not available right now in one of those programs, and you want to add that feature, but it will require a developer to go in and actually make that change. Well, in Coda, if there's a feature that you would like to see, you can actually build it yourself because of how powerful the formula language is and how powerful the tables are in Coda. That's another advantage for using this template for managing your projects, is that if there's a specific feature or a specific filter or a specific format, you want to see your data, you can do it on your own without needing to be a developer or programmer, and that's a core concept we talked about in Class 2. In terms of an overview of this section, this is just like an introductory to the Product Launch Hub. You can see how as a quick start you can write your vision, fill in details by your teams and tasks, you can have your teammates from other teams write their vision and their tasks, and you can also see an overview of a project as well as have an email update section. This is also a nice little Table of Contents for you to quickly go to different sections on the doc. We have Teams and Tasks, Urgent Tasks, so on and so forth. Just take a read through this first section and in the next lesson we'll actually go in and start adding some tasks to our main table. Please go on to Lesson 9 and take a look at this template as you need.
9. Launching Your Product: Tracking All Tasks: Welcome to lesson 9, Launching Your Product, Tracking All Tasks. In this lesson, we're going to start adding our own data to the task table as well as starting to create aspects of our product, like writing out that vision and also looking at things related to our product. Please follow along with this lesson and I look forward to hearing your questions and comments. In lesson 9, we're going to continue using the Product Launch Hub template that we went over in lesson 8. We're going to start tracking our own tasks and adding information regarding our own project to the template. If you're a startup and you're about to launch products, or maybe you are a freelancer or consultant and you are managing a project for your client or if you are an existing company, established company and you have a product that you want to launch new features to or new product features too, this it's perfect template for you because you can manage all your meeting notes, your tasks, as well as any kind of information, free-form information about the project inside this. Also, you can also add your teammates who can collaborate with you on the project. If you haven't already, please make sure you have a copy of the Product Launch Hub template. It looks just like this and we're going to go ahead and get started by editing the vision for your project. Think about a project that you're working on right now or product you're about to launch and we're going to start editing this docs so that works specifically for you. In this vision section, you notice that right now we currently have this fake product that's a self-driving stroller. This piggybacking off of like self-driving cars we currently have right now and for I guess this practical before all the super busy millennials who don't have time to walk the strollers themselves. It's scary, but this is just a fake project. We're going to delete all this information right here and start adding in information about our own project or a product. I'm going to call this AL's, like, let's call this Visionary Skateboard product. The vision for my product is like the vision for this product is for everyone in the world to have a self-driving skateboard. This is just a fake idea and I think this idea already exist, so It's not super visionary, but this shows that you can add it whatever kind of free-form text or emojis that you can put into the doc. I'm going to make this a little bigger. You can also add images by going to this plus sign and then going to image. You can pick an image from your computer. This is where you would put the vision for your new product or if you have an existing product that you're launching can bring the vision here. Now let's click on the teams and task section to give you as the project manager and overview of every single team and all the different tasks associate with the teams right in one place. You notice that there's also at the very top of the section, some metrics about the teams and task. We can see there's four teams. Notice that this is just simple symbol of teams.Count, where we talked about these formulas in class 2. Then here, is also another form of just all the tasks. This is the task table and the count. Here's a team's. Let's actually go ahead and add a team here. These are all again fake teams for the preexisting stroller idea. I'm just going to add another team here by hitting a plus. I am not going to put an image there for now, but I'm going to call my team skateboard manufacturer. This is also obviously a hardware type of team. I will say this is our manufacturer for producing our skateboards. Now you'll notice that right here, these numbers are all zero and these are also calculated. These are all the remaining columns are all calculated. These are like calculated formulas in a pivot table. But since I have no tasks yet for my skipper manufacturer, that's why these are zero and that's why the remaining all of these columns are also empty because I've no tasks. Let's go ahead down here and start adding some tasks. These are all existing tasks that we have. Then you can delete these or just keep it there for now. I'm going to the very bottom, you start adding a task. Maybe that's one task is send draft design of skateboard. We're going to pick our skateboard manufacturer for now. Is it urgent? Let's call it urgent, yes and notice how there's a conditional format word automatically turns into red. Again, you can actually do the formatting despite going into the column here. Actually can you do it from this menu? Actually you can't. You have to go at the very top and then click on this icon right here. You notice how when there is an urgent a task, it's good marks as red. That's fine, and let's say this is in progress and it's starting, let's say, on June 11th. Actually, I think it actually automatically moved it because it's sorted by date. This is here, is my draft design on skateboard and say it's going to take about 20 days to complete. That's going to end on July 1st and notice this is automatically calculated based on the start date and it's going to be assigned to me. Let's add another quick task and we're going to do some really quickly. Let's call this skateboard prototype. Again, let's do this for our skateboard manufacturer, it's not urgent. Let's say this one done, just for sake of argument, this one is done and like gets crossed out right now. It started on, say May 28th. Did I say that right? Yes. Actually where did it go? Let's see if it might have moved up here once since I put the date so far back, it's right here, Skateboard prototype. Let's see here I showed you that thing I just skateboard prototype. Let's say this ultimately took 15 days. It ended on 6/12. Again, we'll assign that to myself. Now we added two tasks to this giant table. We go back to the very top. You'll notice that now our teams, our skateboard manufacturer team now has all this data field out. Remember how we made one of the tasks done. That means it's 50 percent complete because there's one closed task, that was the skateboard prototype that was completed. There's two total task. It started by 5/28, which is the earliest task, and it ends on 7/1, which has the latest task. There's 24 days left until the launch. Notice how this is a nice clean way of seeing all the different tasks and when they're due. The first thing you may be asking yourself is like, this task of look super complicated and very, very big. There's many columns and as we've mentioned in class 2, that's completely fine. You want to have a table that has all your data in it. Because what we're going to do is our building views of this huge table. We just collapses. You can see the whole table. I mean, I agree it's a huge humongous table and it looks super messy. But the key thing to remember here is that we want to have one master table so that once we start building views, we can hide allow these columns, we can group things. For now just imagine that this is one big table we're actually, when you're working on a cross-functional project, you won't be adding to this table one by one like we just did in this lesson. You're going to be adding it by team by team and we'll go through that in the next few lessons. But just keep in mind that if you think table is getting messy, that's totally okay and Coda, we want one table to have all your data. Because once you're building views, you can clean your data up really easily. That's it for lesson 9. Hopefully you got a test of how you can start managing your teams and tasks in this template. We're going move on to actually using the template for individual teams that you may be managing as a Project Manager. Please go onto the next lesson.
10. Launching Your Product: Teams: Welcome to lesson 10, launching your product teams. In this lesson, we're going to look at just the team's table within the Product Launch Hub template, and we're going to see how we can look at just the data solicited for our team and look at how we can write the vision, look at them tasks, as well as look at the meeting notes just within our team. Please follow along with this lesson. In lesson 10, we're going to continue using the product launch hub template we've been going over in the last few lessons. This time we're going to focus on probably the most important part of any project manager's day-to-day is how you've managed your teams. Whether or not you're a large company and you have a bunch of different teams within your projects, or you might just be an independent consultant and you don't really have many teams, but you still have other parties like your clients, and maybe you have an assistant, or you might have an accountant, and those individuals are considered like team, so to speak, because they're all collaborating with you on a project, the teams are the most important part of any project, and we make it very, very easy to use in this template. Let's focus to this lesson just on how you can have your teams get involved with your project and so that you can see their updates, and they can also see any updates for the entire project. If you haven't already, please make sure you have a copy of the product launch hub template. It looks like this. Just makes sure that here says product launch hub in the very first section, and we have a bunch of, I have a bunch of tasks for us to work on together. Let's go ahead and get started with the teams part of this lesson. The first thing I want you to do is, skim the vision for the mapping, industrial designs, sensors, and packaging teams sections. If you go back to the template, you notice that there's four teams: mapping, industrial design, sensors, and packaging. This goes back to the teams and tasks that we saw here, where there's these four teams that came with the template. I added this skateboard manufacturer in the last lesson. But notice how before they're just four different teams here. If I go to mapping, click on the "Mapping" folder, he knows that the mapping team has their own vision. This is just like their specific vision. Industrial design has their own vision as well. How they want to create a stroller that can withstand rough terrain. They also put in some other tasks or some of the features into an in scope, out of scope table. It's really cool because every team can have their own little wiki for what they think is the vision for their team. Imagine if you were a big company and you are launching a cross-functional project, all your different teams can put their visions in just one part of the dock. This goes back to class one where you don't have one individual Google Doc for each team, and it's all sitting in other folders, these are individual Google Docs all in one place for a year to manage, for you to see to have organized in one place. That's how the vision works. As you're building out your teams, you can have your team's write their vision here, you can rename these folders and sections, of course. Why don't we just go and do that? I'm just going to rename this to my skateboard section because I did a skateboard, skateboard manufacturer in the last lesson, manufacturer, and this is the, let's call this the manufacturer vision. This would be my vision for my skateboard manufacturer, or the skateboard manufacturer will be going in here and writing their vision. You can have your team members write their vision here as well. We're going to now view the filter on the Mapping Team Tasks view. Remember, in lesson 9, we talked about how there's a really big, messy table in the Teams & Tasks section. This is the master task table for every single team and all different tasks that we're working on. We said it's okay if it's super messy, we're going to go look at just the mapping team. Actually, this was the original Mapping team. Let's go back to the Mapping Tasks table now. If you look at the Mapping Teams Tasks, if you go over here and we hover over the title and click on that link sign, you notice that when we've seen this before and in various other templates, but Mapping Tasks is a view of the tasks table. The task table is a big, messy one that we have here. This big table right here. Mapping Tasks is just a view of the main task tables. What's really cool is that the mapping team can just see what's important to them on their portion of this doc project, this Project Launch Hub doc without having to skim through this massive messy table. Hopefully, you can see how powerful these views are. I wanted to look at the filter for just this Mapping Tasks view. If I click on this filter icon, you notice that it just says, team equals mapping. Team is actually a column in the teams and tasks table. Let's go back to Teams and Task really quick. Notice how team is right here, there is industrial design, packaging, mapping, and mapping is one we care about. If you go back to Mapping Tasks, you notice that even though these view is filtered on team equals mapping, the team column actually isn't here. This also best practice is that since you already know that this is a mapping team view, you need to have the team anymore as a column and it reduces the clutter in your view because you already know that by default this is filtered by the mapping team. We just had to put in the relevant columns that we wound, which is, who is the task assigned to? It's all these people right here, one is the start date and number effort days. You notice that also here we can quickly see whether or not the task has been not started, done, or in progress. Remember this grouping is just, by doing this, group and ungroup. This is what the table region looks like. You can also ungroup this as well. This is the total ungrouped list of tasks. But it's not very informative and user-friendly. That's why as best practice, you should group things that have multiple categories. Status, group this first belong left. The point of group people. Now we know all the tasks and it looks like Polly Rose has two tasks associated with her. This is just, again, view just for the mapping team. We just did, we just ungroup the status and assigned to columns to see how the original table looks like. But this is a much more user friendly view because you can see everything by a big category. This is similar to a pivot table in Excel or Google sheets, but just much more easier to use. You can change data here. Remember that everything is bidirectional, so if I say, this is actually going to be 20 days for this Create new user onboarding flow parent. That 20 days that I change right here, was going to be reflected in the master table right here. As a project manager, you can go in and tell your team members go on and take a look at your view of other tasks, and change the start dates and change the tasks and assign people as you need to do so that everything gets updated in the master table. This something you can't do with a pivot table in Excel or Google sheets because once you create pivot table in Excel, it's a fixed and you can't change the data in the pivot table unless you change the underlying data. In Coda, the view is like a pivot table, but you can actually change the data in the pivot table and it gets pushed back down into the master table. This is another key concept to think about as you build out these views for your teams. We're going to add a task now to the mapping team. Let's go ahead and do that really quick. Let's say I want to add a task to the not started list, and go over here to the tasks column, and I hit the plus sign right there. Also we want to make sure this is for Adam Davis. Let's say, we want to add a task of Make sure map includes city names or something. We can have a start date of June 11th and make sure it's going to say, it's going to be 15 days. Actually, let's put this way out in the future. Let's make it all the way in January 2019. I want to show you how this data will actually flow back into the master tasks table. Let's go back into teams and tasks. Notice that down here, the reason why I put it out in the future is so that it would go down to the very bottom of the list on the master tasks table. Notice how I, just gets added to this row. Now everyone can know that there's a new mapping tasks that is due on January 19th, and it was added by the mapping team right here, and it's assigned to Adam Davis. Hopefully, you can see now how powerful this views are. I'm just going to hover really quickly over some of these meeting notes. These are the meeting notes for just the mapping team. What's really cool is you can put formulas or app references right inside the doc. This is like a, just a Google Doc where you're keeping track of your meeting notes. But if you look over here, you can actually hover over people's names, and that gives you their email address and gives you a nice picture, and these are all based on just your Google account. Anytime you mentioned these people, these are just mentioned like this, like Adam Davis, like that. Right now doesn't work because these people are not actually part of my doc, but anytime you mention people and they show up like this, they'll actually get a notification saying, hay, Polly Rose is, you are given notification on this doc that you're mentioned in. Additionally, you can put in references to features. This is a feature Build wireframes of Android UI, and you notice that when you hover over it, you can actually see all the details associated with that given row. Like who is assigned to, the progress, the start date, so on and so forth. If you click on this, you get the row detail. You can see every single thing associated with that row and you can change things here. As you see for this might be changed let's say to, not started, build wireframes with Android UI. If we go back to the mapping tasks, you notice that build wireframes with Android UI is now not started. Before this was in the done column, I believe. Remember how we added, make sure map includes city names here to Adam Davis. Let's say here we had a new meeting, let's say today is going to stand up on June 6th. I already forgot what was the task called, it was called, make sure map includes city names. Right here I can say, the @make sure, you notice as I start typing, make sure, it automatically auto completed. I can just hit "Tab" here to include that task. Task was added. Look, if I hover over this, it shows me all the details of that row I just added as a mapping team member to the Mapping Masks table. If I click on the View details here, you can see how it's assigned to Adam Davis, it was 15 days. I can mark it as urgent now, and if I go back to the mapping task table, you notice how this is now urgent and it gets that red formatting. I know this is a long lesson. Hopefully, you can see how powerful this view is for your teams. I didn't want to spend a lot of time here because this is probably the most important part of this Product Launch Hub, is because Product Launch Hub template is that you can have your multiple teams go into the dock and edit things as necessary. Thanks for watching this lesson. We're going to go on to Lesson 11 next. As the project manager, you get a bird's eye view of all the tasks that are taking place in your project. Please follow along in the next lesson.
11. Launching Your Product: Bird's Eye View: Welcome to Lesson eleven, Launching Your Product, Bird's Eye View. In this lesson, we're going to look at a high level overview of our cross-functional project off of the product launch hub template, and we're going to see how we can control the table of data using a drop-down or a control, as we call it in Coda to view specific data. We'll also look at a Gantt chart to see how our entire project is tracking towards specific dates. Please follow along in this lesson. Welcome to Lesson eleven. We're going to continue using the product launch hub template we went through in the last lesson. Hopefully in the last lesson you were able to see how you can have multiple different teams, you can look at their vision and have multiple tasks associated with just those individual teams, and how powerful this is because you can edit the tasks just for your team and how it flows back into the entire model and template. In this lesson, we're going to look at the view from the project manager's perspective. If you want to bird's-eye view the entire project, this is the lesson where you are going to see how you can use that approach where you can see how everything is going through entire project and looking at how your all your different teams are performing. If you haven't already, please make sure you have created this or opened this template. It's called the Product Launch Hub, and again, the links are in the dock right here, best way is to click on this link. If you click on the Launch Status, I'm just going to collapse some of these folders here, this is the high level overview of all your entire project, as well as all different tasks in your project. Notice how there this nice little Gantt chart here. Let's just do a few things here. Notice how the Stroller Launch date is nine, nine, I want you to change the launch date on the Launch Status section. We're on the Launch Status section, let's change it's date, let's say to, instead of September 9th, let's make this October 1st. You notice how a few of the conditional formatting changes, is because the conditional formatting and the Gantt chart is based on when the start date is. Let's change this back to September 8th. We're going to go through that conditional formatting in just a bit. The next part is pick and choose one or few teams in the team drop-down. The drop-down is basic control in Coda. Right now you notice how I have this locked as all. Let's say I only want to look at the tasks for the Mapping Team, so I can actually get rid of packaging, get rid of sensors, get rid of the rest of the design. Skateboard Manufacturer was a fake team I created back in lesson nine I believe. I'll get rid of this as well. I only have the Mapping Team selected and now I can just see the tasks associated with the Mapping Team. Also I can see some formulas here that are related to just the Mapping Team. So nine tasks remaining, and there's four tasks that need attention. You notice that this formula right here is built off of the launch tasks view. We will go through this Gantt chart in a bit. But I just want you to see how you can change the team here on the control and everything else will change below. All these numbers, the Gantt chart of all the tasks. You can see how dynamic this is as a project manager to see all your data for all Teams, or you can just drill down into one specific Team within your project. Let's now view the formulas at the top of the launch section to see formulas mixed in the Canvas. We walk through this just now a little bit. But the main important thing here is that you can put formulas into the canvas. We've talked about this a lot in class two actually, but right now let's go back to just the Mapping Team. You notice the formula here is just launch date minus now. We know that this is September 8th in the future and today is actually June 6th, I believe so there's 92 days left until the launch day. This gives you like a nice countdown of when the project is due. It's a little scary for project manager, but it gives you a little bit of fire to get things done. These tasks are just taking the launch tasks associated with the Mapping Team and just counting the total number of tasks. Remember how we talked about how you can do different filters, so this is the table launch tasks. The filter end date has to be greater than launch date. That just means that this task is past due and then you're counting the number of tasks that are past due. This is is also a nice formula that gives you a bulleted list of all the tasks that are past due. While this formula right here was a count of your past due tasks, this is a bulleted list that actually writes out all the tasks for you, which is a right nice feature. Since these are formulas embedded into the canvas, you can hover over each value to get specific notes about that task if you want to. As a project manager, what this allows you to do is see again at the very high level, all the different tasks for a different Team within your project. But if you want to, you can drill down to the nitty-gritty for the task by hovering over each task and just scrolling and seeing what's the actual detail behind that task? Why is this task past due? You can actually notify the Team member on a Mapping Team about, hey, I saw that create-new-user-experienced child is past due. What's going on? I can ask Lola here for the reason why. But again, this is just a bird's-eye level view. Now we're going to make a call out to the number of task Mapping Team has by writing a formula in the canvas. This is actually already done for us. We have nine tasks for the Team. We can skip that one, but if you want, you can just try writing this on your own over here. You could do it two ways. We can do launch tasks dot count, which is just this table, dot count, or the longer way is if we don't want to use this view, we know that we have the master task here which we just call tasks and we can do a filter. Remembers it's table then filter. Filter left parentheses where team equals mapping, and then do a dot count. Let's look at this from a really quick. We have the table, the filter. We're filtering by just the tasks where the Team equals Mapping and then we're counting all those rows. The reason why it's 11 is I believe there were a few tasks that are not caught in this filter. Let's take a look here. This number includes tasks that are done. That's why this number is greater than that. I think what we could do here is just do Mapping task and status does not equal done, and that should be nine. There you go. This view, we'll talk about this in the next section. There's two ways of writing this number, given the number of tasks that are not done which is being launched as a count because this Gantt chart is already filtered by tasks are not done. This is a second way of writing the formula where you have the whole task table filtered by the Mapping Team and the status go down, and then we just count that. Critic conditional format on the Gantt chart for tasks with an end date greater than launched minus three days. We're going to create conditional format for tasks that are basically coming close to do, and we want to see them with a different color. Let's go back to all the tasks. I'm going to delete these numbers for now. You notice here if you hover over the task Gantt chart, there's a conditional format of end date greater than launch date minus ten. This is basically looking at tasks that are coming up. If a task is due within ten days, it's going to get marked as an orange. That's why there are some of these are marked as orange. All of these other tasks for all the other teams are basically still have some time to work on them. If we want to get even further out view of our tasks, we do end date greater than or equal to today, or sorry, launch date minus 30 and I say that enter right there. Let's give this a green color right there. Now we have three conditional formats recently they were only two now we have three conditional formats. Let's get out of this. Now you can see some of these tasks are coming up within 30 days of due time. Out of all the tasks, you can get a quick level overview of what tasks are due within ten days? What tasks are due within 30 days? Which are the green ones? Then what tasks are already past due? which are the red ones down here. The blue ones are just the ones that have greater than three days to finish. That's how you can do conditional formatting for your Gantt chart. Now the last thing, let's move some gantt charts around to see how dates and conditional formats change. Remember that launch tasks is a view of the main task table. Anything you change here will alter the main task table. Also remember that this is filtered by tasks that are not done and also contains the team selectors. It contains a new formula we haven't talked about, but it's very similar to matches. This is a control where you can pick the Team and whatever Team you pick here controls the filter that shows up in this contains Team Selector. Teams Selector is just the name of this control. Let's go down and filter this team-down to adjust the Mapping Team again. Like that, and you notice how we have a few tasks here. Now you can actually drag and drop, you can also click on these icons, these bar charts or Gantt charts to click on and get the actual detail. But if you want to extend a due date of the end date that project, you can you just expand that like that. This will change the start date and the end date for that task. This is another example right here. If I click on this guy right here, you notice how we can't see that the text here but if I click on this now, and also the start date is 6/18/2018 and end date 7/7. Let's say I change this to June 1st as a start date, June one. Actually, it's going to be a little hard. This is May 28th and let's change our end date to some more time in end of July. If I look at this build wireframes of Android UI, notice how this automatically changes the data of 528 to 730. Then I go back to the mapping tasks. It's the skipper Manufactured task table now. I change the build wireframes here if I go to mapping tasks, build wireframes also changed to 528 and end date is a hitting column. But basically what I'm trying to show you here is that, as you're changing the Gantt chart, it changes all the underlying data within the tasks table. If I move this forward by a little bit, you notice how the color can change, because now it's fitting within certain conditional formats. If the end date is getting close to within 30 days of being due of the launch date, that's when the colors are coming into play. Actually, as you move your tasks around, the colors will change based on the conditional formatting, which is really cool. You notice how the text here is changing as well because now some tasks are past due, some are not past due anymore. It's a really interesting way to visualize your data and to also see how your tasks are getting due or past due and by applying the conditional formatting, you can quickly figure out whether or not the task is due or past due. This is just getting a specific view of the Mapping Team. You can do this for your entire Team right here and move things around. As you moving things around, remember the dates for the start and end all change for your project. Hopefully this gave you a nice overview of how you as a project manager can see all the task and all the teams for what your team is working on for launching the product. This gives you as well as all your team members, an overview of how you're tracking against completing your project. In the final lesson, we're going to talk about how you can communicate to your team members using an e-mail template that is set up in your Coda Doc. Please follow along for the next lesson.
12. Launching Your Product: Communication: Welcome to the last lesson of Class 3, Launching Your Product Communication. In this lesson, we're going to talk about how to create an e-mail template based on all the tables and data from the Product Launch Hub template you've been using for the last few lessons. We're going to talk about how you can use formulas in the Canvas, how you can structure the words and the numbers in such a way so that you can copy and paste your data from Coda right into an e-mail. We'll also talk about additional project management templates you can look at on the Coda website. So please follow along with this lesson. All right, you made it to lesson 12 in Class 3. If you've taken all the classes so far, congratulations, you've completed beyond Excel. Hopefully, this lesson will drive home the final feature of our Product Launch Hub template, which we've been going over for the last three lessons. In this lesson, I want to focus on just communication. In Class 1, we talked about a lot of the issues with documented communication workflows. One of them is, how do you communicate to your team members about your projects? How do you communicate to your team members about conversations of having your customers and users of your product and so, in this lesson, I'm going to focus on just how you can communicate the status of your project to your team members using e-mail. We can also talk about how you can automate this a little bit, but for now, I'm going to show you how you can create a basic e-mail template in Coda, in the Product Launch Hub template to educate your team. Again, if you haven't made a copy of the Product Launch Hub template yet, please go to this link here and it should look like this for you. The first thing we're going to do here is change the date range for the e-mail to see date changes in the e-mail templates. We went through the entire Product Launch Hub template in the last three lessons. Our very last section we're going to look at is the e-mail update. What's really interesting here is that this is an e-mail that you can literally copy and paste into Gmail or whatever mail you use. But what's really cool is that all of these numbers will change based on the date that you select in the date range. Right now, it's set from May 1st to May 31st, and all these formulas here are built off of this date range. What's really cool is that this date range as you click on it, will actually change these numbers. If I change this to last month, like those last 30 days, you notice how this change a little bit. If I go to, let's say, last month, basically these bullet points underneath will change. Actually, these numbers don't change, it's actually the text that will change because this text is actually, here's the formula here, it's looking at the date that you pick in this date range picker, and it filters by all different teams and whether or not the status was done in Chris bulleted list off of that filter. This is like a complicated formula to look at, but if you have any questions, feel free to e-mail me. I'm not going to walk through exactly how this formula works, but just know that in this template itself, you can pick whatever date you want. I'm just going to do different date here, I'll say let's do somewhere in the future, July 1 to July 31st. It just allows you to change things in the e-mail templates so that you don't have to manually type in, oh, now it's July 1 to July 31st, and here are all the tasks that need to be completed or are complete, everything just changes dynamically. As you're completing tasks, these percentages will also get checkoff as well. Let's actually try doing that right now. Let's go to Industrial Design and let's check off a task. Right now, it's at 13 percent, let's say I check off, watch it interestingly in Industrial Design, they did a Trello card view. If I move this from here to there, I move this from here to there, let's see if our percentage increases and it should in theory, there we go. Now, it's 40 percent and that should include some of the task that were DOB based on this formula. If I remove tasks from the Done column, that number should be down from 40 percent, of course, so now it's down to 20 percent. Hopefully, you can see now how you can actually get a dynamic e-mail template that changes based on the data from your teams and from your tasks. Well, let's actually create a formula now in the e-mail template that changes based on our data. We're going to show the number of in progress tasks that each team has. This is going to be a simple formula. You notice how for here, this is a formula that shows the Sensors team, and we're actually not going to worry about the date for now, we're just going to look at whether or not the task is in progress. For Industrial Design, I'm going to say in progress tasks. Now, the filter formula is equals, it's going to be tasks, is our main tasks table. Now, let's do our filter. So filter for where the team equals industrial design and the status, going on here, hit "Tab", equals in progress. I can actually use my arrow keys right now, hit "Tab" again. I have my table, I have my filter, and now I wanted my action which is count. So I count all the tasks for the industrial team and also in progress. I'm going to hit "Enter" here. Now I know for my entire Industrial Design team, there are four tasks that are in progress. Let's actually do this for every single team really quick. I'm just going to copy, you can actually just copy everything here, like that. Control Command C, Command V. I'm not going to change the formula so that I have to retype everything, this is going to make this so it says Sensors tab. I'm going to do the same thing for here, in progress tasks. I'm going to change this formula to be mapping because this is the Mapping section. Mapping. For packaging, same thing. Let's do this for packaging. We just added a in progress, this is not really well-formatted, but now I was able to add to my e-mail templates the number of in progress tasks for each team, for Industrial Design team, for Sensors, Mapping and Packaging. You can see how flexible that this can be because now, I can literally just command, copy this, throw into an e-mail template and send it off to my team. I don't have to worry about updating these numbers and changing the text here for these different bullet points. They're all just going to works because I've set up this template to work so that it changes dynamically based on formulas in the Canvas. We basically walked through how to change the date range, how to create a form on the Canvas to create the in progress tasks. This is basically how you can use Coda to communicate with your team in a much more dynamic way that reduces a lot of the manual nature of copying and pasting from your Google Docs into your e-mail, or copy and pasting a number from Google Sheets or Excel into e-mail. This changes dynamically based on all the tasks that are in the master tracker and also based on whatever your teammates are doing within their specific team views. That wraps up the Product Launch Hub template, it's really advanced template, but I think if you take these last four lessons from 3.9-3.12, you'll have a really great understanding of how to manage your project, whether you're a startup, independent consultant, you're managing for your clients or you're a large company and you have a large product with cross-functional teammates that you need to coordinate on for a project. There are many additional project management templates that we have on the Coda website. Coda is actually meant for project managers. We built the tool to really make it for project managers. If you click on the link in the last bullet point, there is a bunch of other templates you can use. Maybe you like using a Kanban chart or there's also a mini version of the Product Launch Hub. There is a simple status updates template. All these templates are used by real users and companies right now with Coda. If you find any of these things useful, definitely check them out. I want to thank you so much for taking lesson Class 3, you went through a really important set of templates. Again, if you have any questions, feel free to reach out to me on e-mail or you can click on this question mark here and hit "Contact Us" and it'll give you a nice chat box to talk to people at Coda about where you're working on your template. Hopefully, everything you worked on in this whole class will help you with the class project. I look forward to seeing your projects and I also look forward to seeing how you're going to use Coda and use the various templates that we talked about in this entire class. Without further ado, get started on the class project.
13. Outro: Congratulations. You have finished class number three, Beyond Excel 3 in this Beyond Excel series. Over the course of three classes in this series, you've learned about basic productivity tools with a specific focus on Coda, a productivity tool. Also, templates that we discussed in this class used by independent consultants all the way up to Fortune 500 companies. So given all the things you've learned in these three classes, you now have the superpowers of developers and programmers to build amazing tools for sales, for marketing, for product, for HR, the possibilities are endless. So instead of working in tools that haven't changed that much in 40 some years like a doc or a spreadsheet. I hope you can give Coda a try because Coda has the flexibility of a doc, but also the power of a spreadsheet. So this is just the beginning of your journey in Coda. I would love to see the templates that you build in Coda, so please email me with your templates. If you have any questions, feel free to reach out to the support team at Coda. I look forward to seeing your projects as you finish up the classes and lessons throughout the Beyond Excel series. Thank you again for taking this class and I look forward to seeing what you can Coda.
Al Chen, Excel Trainer & Coda Evangelist
