{"id":844,"date":"2020-07-17T13:27:56","date_gmt":"2020-07-17T13:27:56","guid":{"rendered":"http:\/\/blog.majeros.atthost24.pl\/?p=844"},"modified":"2023-12-06T09:05:15","modified_gmt":"2023-12-06T09:05:15","slug":"tools-x-sections-space","status":"publish","type":"post","link":"https:\/\/knowledgebase.privmx.com\/pl\/tools-x-sections-space\/","title":{"rendered":"(Tools x Sections) space"},"content":{"rendered":"<div class=\"wp-block-jetpack-markdown\"><p>What are the key ingedients in our recipe for a digital collaboration workspace? It\u2019s been a real achievement to describe it in a single blog post, so don\u2019t miss it. \ud83d\ude42<\/p>\n<p><strong>In two previous posts, <a href=\"https:\/\/knowledgebase.privmx.com\/pl\/why-privmx\/\">Why PrivMX?<\/a> and <a href=\"https:\/\/knowledgebase.privmx.com\/pl\/privacy-by-design-means-care\/\">Privacy-By-Design means Care<\/a>, I started to describe our motivation and ideas shaping PrivMX as a contemporary, human-oriented digital workspace. Here, in the third and the last post of the series, I\u2019d like to complete the picture with a short presentation of the most important ingredient &#8211; the (Tools x Sections) workspace architecture. This is the core functional concept of PrivMX, originating from somewhere between project management, user experience and interface. Let me outline the thing below.<\/strong><\/p>\n<h2><strong>Fusion of Tools<\/strong><\/h2>\n<p>One can say that the selection of tools shapes the workspace \u2013 that\u2019s why we spent a lot of time making difficult choices determining the first set of PrivMX collaboration tools and their configuration. There are many possible ways you can make such a selection; we decided it should be dictated by the needs of new teams. We belive that the moment of starting a new project is essential and fascinating and that each team needs some time to figure out how to work together, how to organize communication, share tasks, etc. In effect: each team organically creates its own, original environment, an ecosystem of sorts \u2013 but it happens only if the workspace is elastic enough to allow it to happen.<\/p>\n<p>PrivMX workspace is designed to support such <strong>organic processes<\/strong>. It\u2019s like a clean canvas on which every team can create its own structure and workflow. In a way, it\u2019s both <strong>agile and method-agnostic<\/strong>, as it allows management to take various forms, depending on the context and the needs of people. We\u2019ve been trying to minimize the number of objects and relations involved, so the collaboration tools we made available inside PrivMX are the most fundamental and simple ones. Chats, files, tasks, calendars, etc, are useful for every team from day one, allow to start quickly and develop.<\/p>\n<p>Our tools are interconnected, using natural relations between objects, and there is no data duplication &#8211; the same object (a file, for instance) is available from different perspectives (tools), in different ways. This helps team members to find their own path in team\u2019s common digital space. \u2018Fusion of Tools\u2019 is a short name we chose to describe such mixture of tools and objects within the workspace.<\/p>\n<h2><strong>Divide and conquer<\/strong><\/h2>\n<p>In our opinion, there\u2019s one more special element necessary for team developement to stay organic and really effective &#8211; a simple method of dividing workspace, yet another tool available to all team members. There simply should be no need to ask or wait for anyone to organize work \u2013 everybody should be able to participate in bringing order to initial chaos. After all, every project starts from chaos, right?<\/p>\n<p>In PrivMX, we introduced a mechanism called Sections to deal with complicated matters. When a certain aspect of the project becomes to big to grasp and overshadows other important aspects, any Team Member can create a Section (or a sub-Section) to seperate it and manage it better. Or when there is a natural division of roles among team members. Or, generally, when there is simply a need for a separate, shared space with some particular functionality and purpose. Each Section can be configured differently, with a personalized selection of tools, separate storage space, available to a selected group of team members or for the whole team.<\/p>\n<p>It may look simple or obvious for someone these days &#8211; and to be honest &#8211; it is simple! It\u2019s the simplicity that makes Sections so powerful and flexible. The real power, however, comes from a combination of Sections and the Fusion of Tools. Discovering that Sections and Tools naturally form a coherent two dimensional desktop was a true \u201eWow moment\u201d for us. This idea became the basis for navigation within the app &#8211; you can test the effect in PrivMX by yourself.<\/p>\n<p>If it comes to organization of work, I think it is worth to mention two more tools here &#8211; Lists (of Issues) and Mind Maps. These are especially fiendly to all analytical minds and organizers and help them a lot on the battlefield. Together with Sections and other tools, they make PrivMX a real all-in-one, <strong>digital swiss army knife<\/strong> \ud83d\ude42<\/p>\n<p>OK, I think that I should end this short introductory blog series here. There are many details I have not covered so far, but I will surely get back to them later. For today, I hope that you have a better feeling what our \u201eTools x Sections + Care\u201d pink cow is about. \ud83d\ude09 If you are reading this line, I certainly must say it again: thank you for your interest in PrivMX! Please consider giving our software a try, and don\u2019t forget to let us know what you think.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":7,"featured_media":845,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[2,9],"tags":[],"class_list":["post-844","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-privmx-origins"],"jetpack_featured_media_url":"https:\/\/knowledgebase.privmx.com\/wp-content\/uploads\/2023\/05\/blogpost4cover-1.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/posts\/844","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/comments?post=844"}],"version-history":[{"count":3,"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/posts\/844\/revisions"}],"predecessor-version":[{"id":2427,"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/posts\/844\/revisions\/2427"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/media\/845"}],"wp:attachment":[{"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/media?parent=844"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/categories?post=844"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/knowledgebase.privmx.com\/pl\/wp-json\/wp\/v2\/tags?post=844"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}