# 'Project' is now 'system' > An update to a fundamental Johnny.Decimal term. Until now, I have used the word 'project' as a term to mean _the thing that you're organising_ and/or _the result of doing the organising._ For example, the Workbook's cover sheet reads: > A guide to setting up a single-project system and working the Decimal way This is imprecise and confusing. What if you're not organising a project? This results in me having to qualify it, for example: > Yours might not feel like 'a project' in the typical sense. ## Precision In defining this system, I believe that precision and clarity matters. I want to help you to be more organised. If you're confused about what I mean, that's just going to get in the way. And if we all use different terms when we discuss things on the forum, we're going to be talking across each other. ## New definitions With a lot of [community consultation](https://forum.johnnydecimal.com/t/jd-what-is-a-project/1181/1) and [intense whiteboarding](/blog/0028G-Whiteboard-1280x960.jpeg) here at JDHQ, we've come up with the following definitions of terms. The site and Workbook will be updated to reflect these new terms. (This will improve clarity, but nothing fundamental has changed.) I'll add a new page to the main site with the definitions minus the background contained in this post. --- # The Johnny.Decimal System _Is a collection of methods, tools, and behaviours as documented at johnnydecimal.com._ **Defined terms:** - `The Johnny.Decimal system` - `The system` (for short) --- # Your Johnny.Decimal system _Is your implementation of this system, customised to suit whatever it is that you're organising._ **Defined terms:** - `Your Johnny.Decimal system` - `Your system` (for short) We considered the repeated use of the term _system_ here but it's just too natural a word to ignore. It's a very 'active' word: a system is a machine, an organism. It has components. It evolves. And _your_ system is just an implementation of _the_ system. They're the same system. Your system is shown 'breaking out' of the bottom of the Johnny.Decimal system to indicate that it's customisable. You don't have to follow my 'rules' to the letter (although I think you should). --- # Components _Johnny.Decimal systems are made up of components._ **Defined terms:** - `Components` or `system components` The list of components is not restricted, but the following are all common components: - The index (see below). - File system. - Notes (either an app or on paper). - Tasks, to-dos, and reminders. - Email. - Calendar. - Bookmarks and other saved links. ## The index _The index is a specific component of your system; it serves to link all other components together in to a cohesive whole._ **Defined terms:** - `The index` or `your index` --- # Your stuff _Your stuff is the real-world thing that you're organising with Johnny.Decimal._ I can't specify the thing you're organising – because you can organise anything you want. It's your home life, or your job, or a work project, or a community group, or your university study, or _anything else._ **Defined terms:** - `Your stuff` (yes, really) --- # Collection of systems You may need more than one system to manage everything in your life. _We refer to this as your collection of systems._ **Defined terms:** - `Collection of Johnny.Decimal systems` - `Collection of systems` (for short) --- # Domain _Domains group together systems which have one or more shared components._ For example, when you go to work, everything might be on the company's systems: your index, your file system, your email; _everything._ 'Work' is its own domain in this situation. But if you use your personal phone's notes app to keep notes related to the system at work, that app just became a _shared component._ 'Work' is no longer its own domain; it has merged with your 'home' domain. ## Extended naming This is relevant when we consider the extended naming of your systems. A system which is the only system in a domain can be uniquely identified by the [standard `AC.ID` notation](/documentation/acid-notation): - `11.01` can only refer to an item in one system. When a domain contains two or more systems, this is no longer the case: - `11.01` could refer to an item in two or more systems. When a domain contains two or more systems, each system SHOULD[^should] use the [extended `SYS.AC.ID` notation](/documentation/acid-notation/#sysacid). [^should]: As per [RFC2119](https://datatracker.ietf.org/doc/html/rfc2119#section-3), I use SHOULD to mean that I recommend that you do, but that it is not _strictly_ necessary. --- # A note on the word 'project' I've said it elsewhere, but it bears repeating. I consider 'a project' to be a very large thing. In the Workbook we use the analogy of _painting the kitchen._ People colloquially call _painting the kitchen_ 'a project'. It is crucial to understand that _painting the kitchen_ can be handled within **a single Johnny.Decimal ID.** It is **not** what we used to call a project; what we now call a system. You don't need ten areas and a hundred categories and ten thousand IDs to paint the kitchen. So let's _remodel the kitchen._ Does that need its own system (née project) yet? **No.** It could still fit in a bunch of IDs; at most, it's its own category. Let's _rebuild the house._ Full system? **Nope!** Definitely a category; potentially an area. So what does it take to 'fill' an entire system? I say you need to _build a farm._ One area builds you the house. Another might deal with connecting your plot to the local infrastructure: a category each for roads, electricity, and water. One more for setting up a working farm, and we're done with room to spare. ## Think big I tell you this to encourage you to **think big.** Design broad categories. Design _very_ broad areas. Your entire life can _easily_ fit in a single Johnny.Decimal system.> Discuss this [on the forum](https://forum.johnnydecimal.com/t/jd-what-is-a-project/1181/51). > Internal ID: `D85.61.11`.