如何構造更好的團隊

{"type":"doc","content":[{"type":"blockquote","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在 上一篇文章 ","attrs":{}},{"type":"link","attrs":{"href":"https://mp.weixin.qq.com/s/UVIDZ1_hmufR8yiFj57fNQ","title":null,"type":null},"content":[{"type":"text","text":"爲什麼每個程序員都應該瞭解“康威定律”","attrs":{}}]},{"type":"text","text":"中，我們說了開發出來的產品是其背後的組織溝通方式的體現。那麼我們如果有機會去負責一個產品，我們就要首先考慮如何搭建符合我們產品的團隊。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"所以本文是接着上一篇文章 ","attrs":{}},{"type":"link","attrs":{"href":"https://mp.weixin.qq.com/s/UVIDZ1_hmufR8yiFj57fNQ","title":null,"type":null},"content":[{"type":"text","text":"爲什麼每個程序員都應該瞭解“康威定律”","attrs":{}}]},{"type":"text","text":"，如果沒有看的同學可以一起閱讀想用。本文主要是介紹什麼樣的團隊是一個好的團隊，以及我們如何來利用團隊的力量來打造我們的產品。","attrs":{}}]}],"attrs":{}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"背景","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"一方面，在新業務開展或者團隊人數較少時，團隊需要更爲高效的適應當前的環境，另一方面，隨着業務的增加或者組織的發展，團隊勢必會越長越大，團隊之間需要更爲有效的溝通和協作方式。同時，如果團隊想要在業界或者組織內部佔有一席之地，也必須不斷加強自身實力和技術深度。這個時候團隊成員勢必會感到壓力陡增，但是有無法描述具體的問題或者尋找合適的解決方法。這是每個團隊都會面臨的問題。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/a4/a4d8a59e86a3b3ae32614679c41a5788.jpeg","alt":"image","title":"image","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"大多數都會從團隊人數不足，團隊成員能力層次不齊來找原因。但是又有那個團隊敢說自己人充足的，又有多少個團隊能做到每個都是能力卓越的精英。這些在大部分團隊來說都是常態，所以在這個時候這兩個原因明顯不能解決當前的問題。即使我們去招更多優秀的人，結果也不一定如我們所願。因爲問題很有可能出現在團隊的架構和溝通上面。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"鄧巴係數","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/5c/5c40f591c730e04d122c6e9b324a31c1.png","alt":null,"title":"","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":"","fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"根據社會學家Dunbar的研究，","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"團體中可以深入互相信任且share working memory 得人數基本上大概是5 個人左右，極限就是是15 人，而能互相信任的上限大概就是50 個人，當超過150 人時就已經高過了社交認知的上限，就連要記住對方的名字都很難。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"所以根據Google 內部長時間的研究，各個Team 之間得dynamic （動態互動）對於產出的影響，遠遠大於有某個大大在某個團隊裏面。而會影響團隊動態互動的因素有哪些呢？","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Team Size 團隊大小","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Team Lifespan 團隊能固定在一起工作的時間","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Team Relationship 團隊成員之間的關係","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Team Cognition 團隊的認知","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"所以好的團隊的第一個基礎就是 ：小巧竟敢且長存的團隊。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"這裏小的定義大概是5-9人，固定的團隊成員的意思是爲一個目標工作的時間至少一年以上。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"爲什麼要提到至少一年以上呢？因爲根據Tuckman的理論，一個團隊從組成到真正可以產出績效，至少要經歷四個階段：","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"numberedlist","attrs":{"start":null,"normalizeStart":1},"content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":1,"align":null,"origin":null},"content":[{"type":"text","text":"Forming 組成階段：英雄來自四面八方，人員陸續補充進來，很少一步到位","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":2,"align":null,"origin":null},"content":[{"type":"text","text":"Storming 磨合風暴階段：大家要怎麼變成利益共同體，需要花時間習慣彼此","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":3,"align":null,"origin":null},"content":[{"type":"text","text":"Norming 形成團隊階段：團隊逐漸演化出標準的流程方法與默契","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":4,"align":null,"origin":null},"content":[{"type":"text","text":"Performing 績效產出","attrs":{}}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/b6/b6c40d530a66dedd3d4a60fbda0f825b.png","alt":null,"title":"","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":"","fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"但要知道的是，從2 ~ 3 其實是會一直持續發生的，因爲每次有人離去和新人加入，團隊成員的家庭和生理狀況變化，以及隨着團隊成熟度與業務量的變化，都會產生新的化學變化，這也是團隊的績效產出爲什麼會一直變化。不是可以簡單用缺人加人就可以解決的問題。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"團隊優先思考模式","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"團隊優先思考模式原文是Team First Mindset,，顧名思義，就是要利用團隊的力量，就要建立團隊的概念。 進一步說，什麼是團隊優先思考模式？","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"團隊對某個軟件（系統）負責，並且持續的關注與改善","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"團隊會議要承諾參與並且不要遲到","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"團隊對於內部事務要持續討論","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"專注在Team Goal","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"幫助他人移除阻礙","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"培訓新人，互相幫助成長","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"避免爭輸贏的爭論，要能包容探索各種可能性的言論","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/32/320a91b166b0e05c8db23b9db0bf16fb.jpeg","alt":"image","title":"image","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"此外如果要讓團隊能以高效的模式運作，首先要以小巧精幹的長存團隊爲單位，並且限制與減少不必要的溝通，這邊所謂限制不是說讓團隊互相隔離，而是並不是所有的交流的都是好的和必要的，其實就跟系統開發一樣，一開始也許大家都可以互相調用，但是隨着系統變大邏輯變複雜，團隊與團隊之間要建立溝通的規範與API接口。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"而這個溝通的規範就是我們接下來要講的：認知負擔","attrs":{}}]},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"最小化認知負擔","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"thoughtworks等技術諮詢團隊在很早之前就開始調研並擁護","attrs":{}},{"type":"text","marks":[{"type":"color","attrs":{"color":"#1890FF","name":"user"}},{"type":"strong","attrs":{}}],"text":"團隊拓撲","attrs":{}},{"type":"text","text":"這一理念，而團隊拓撲的作者將認知負擔分爲三個種類：","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Intrinsic Cognitive Load （內在認知負擔）：比如說了解Code 怎麼寫","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Extraneous Cognitive Load（外在認知負擔）：比如說要怎麼deploy","attrs":{}}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Germane Cognitive Load（有意義的認知負擔）：比如說Service 之間怎麼溝通","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"那該如何最小化認知負擔呢？就是把稀缺的腦力放在有價值的地方，我們可以透過使用好的IDE和tool或是教育訓練，結對編程等方式來有效降低內在認知負擔。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"透過SOP或是專屬的Infra Team / DevOps Team來幫助建置優化開發部署流程，消滅工程師的外在認知負擔。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"讓工程師更專注在於產生價值的Germane Cognitive Load（有意義的認知負擔），設計更好的系統來解決客戶的問題帶來價值。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"所以當隨着業務量變大以及團隊成長，但是團隊的績效和產出卻開始下滑，並且同仁們開始怨聲載道時，這時候可不能簡單的認爲，應該是人力資源不足加人就好，而是應該是要先從團隊的認知負擔開始檢討。是不是單一團隊承載太多認知負擔了？","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"切分團隊","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"那麼如果說上面分析之後的確是團隊承擔了太多的認知負擔，我們就要考慮切分團隊。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"團隊的切分也是一門藝術，傳統的思考模式是，某個domain / project 變大變複雜，那就找多一點人或團隊一起加入幫忙，於是到處開始資源盤點和借人。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"另一個常見的場景就是，某團隊把某個案子或產品做的有聲有色，於是就會有更多的工作和事情塞給他們，由於績效不錯又幫公司賺錢，所以工作更多的狀態下，老闆也會同意讓他們補更多的人，但是也就越增加他們的認知負擔。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"但是現在我們應該認識到：","attrs":{}},{"type":"text","marks":[{"type":"color","attrs":{"color":"#1890FF","name":"user"}},{"type":"strong","attrs":{}}],"text":"應該要先從把大domain / project 切分成許多sub domain / sub project 開始，再考慮這些sub domain 之間的關係，要分別切分給哪些團隊處理。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/3e/3e7c27e35b1abe8c4324bda84274d2dd.png","alt":null,"title":"","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":"","fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"切分完domain 和團隊完後，也要思考團隊間的協作性，某些團隊之間可能更需要緊密的合作，某些團隊可能只需要維持最小程度的同步。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/cf/cf8e77394335e61d7229b610885485eb.png","alt":null,"title":"","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":"","fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"這不就像是單體化應用切分成微服務的過程一樣嗎？所以這就回到康威定律：團隊的切分與組織的溝通模式會決定你的系統架構。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"heading","attrs":{"align":null,"level":1},"content":[{"type":"text","text":"總結","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"今天我們聊瞭如何建立一個好的團隊，並引用了一些關於團隊建設的理念和知識。一個好的團隊對內一定是有效的溝通，這個就需要我們團隊的規模不能過大，過大就會造成每個人的認知負擔。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"其次，我們需要通過使用工具來減輕團隊內部成員的外部認知負擔和內部認知負擔，讓團隊成員都可以專注於有意義的工作中上。其次要通過培訓等各種方式培養團隊內部的團隊意識，形成團隊優先的思考模式。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"最後就是維護好每個團隊之間的協作，讓每個團隊都將外部的團隊當作自己的客戶，不斷培養外部客戶的習慣來更好的使用團隊產出的產品（文檔，代碼等）。","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":"br"}},{"type":"horizontalrule","attrs":{}},{"type":"blockquote","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"如果喜歡我的分享，歡迎關注“雨夜隨筆”","attrs":{}}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"原文鏈接：","attrs":{}},{"type":"link","attrs":{"href":"https://mp.weixin.qq.com/s/UVIDZ1_hmufR8yiFj57fNQ","title":"","type":null},"content":[{"type":"text","text":"爲什麼每個程序員都應該瞭解“康威定律” (qq.com)","attrs":{}}]}]}],"attrs":{}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https://static001.geekbang.org/infoq/2a/2a30215391e2c965017a9a082ee267a9.png","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}}]}