Switching Productivity Tools - WHEN and HOW you should do it as a Busy Professional

Podcast: Productivity like a Pro!
14 Mar 202423:54

Summary

TLDRIn this productivity session, Paco and the host discuss the challenges and considerations of switching project management tools within a business. They delve into the 'shiny object syndrome,' where the allure of new tools can lead to frequent changes that may not always be beneficial. The conversation highlights the importance of understanding tool-agnostic workflows and the impact of migrating to a new system, especially for larger teams. They share personal experiences with various tools like Trello, ClickUp, and Asana, emphasizing the need for a clear advantage before making a switch and the potential costs associated with it.

Takeaways

  • 📈 Prioritizing tool usage based on business needs and workflows is essential, rather than simply chasing the latest technology.
  • 🔄 Switching project management tools can be a complex and costly process, especially for large teams.
  • 🤔 It's important to weigh the benefits of a new tool against the potential disruption and training costs.
  • 🚀 Established tools with a proven track record can be more reliable for businesses with high task volumes.
  • 🛠️ When considering a switch, evaluate how the new tool will integrate with existing workflows and processes.
  • 📊 Understanding tool-agnostic workflows is crucial before adopting new tools, as it allows for flexibility and adaptability.
  • 🔧 Testing new tools in a controlled environment can help identify potential issues and benefits before full-scale implementation.
  • 🔄 Partial migration of tools can be a viable strategy, allowing for a gradual transition without overwhelming the team.
  • 💡 The 'shiny object syndrome' can lead to frequent tool changes, which may not always be beneficial for productivity.
  • 📈 A pragmatic approach to tool selection and usage, focusing on the core functionalities and performance, is recommended for long-term success.

Q & A

  • What is the main topic of discussion in this productivity session with Paco?

    -The main topic of discussion is about changing project management apps and when it is appropriate to switch tools, considering the effort and cost involved.

  • What was the situation that triggered the discussion on changing apps?

    -The discussion was triggered by a member of the Inner Circle cohort who was犹豫 about migrating his project management tool from Trello to ClickUp.

  • What are the considerations when deciding to switch project management tools?

    -Considerations include the ease of use, understanding of workflows, the potential advantages of the new tool, and the impact on team members who need to onboard to the new system.

  • Why is it dangerous to stick to the same tools without evolving?

    -Sticking to the same tools without evolving can be dangerous as it may lead to falling behind in technology, reduced productivity, and inability to take advantage of new features and improvements that other tools offer.

  • What was Paco's experience with a project management tool that he used for over 15 years?

    -Paco used a project management tool for over 15 years that worked perfectly for his company, despite being an older technology. It had a robust database model and allowed them to handle over 500,000 tasks without performance issues.

  • What does Paco look for in a new tool when considering a switch?

    -Paco looks for a tool that offers a significant advantage, such as easier time tracking using AI, better integration with financial systems, and improved workflows for his team.

  • How did the company Paco was part of handle the switch from Asana to Trello?

    -The company decided to switch from Asana to Trello as the official project management tool. However, after calculating the costs and impacts of the migration, they kept using Asana for certain teams and used Trello in parallel, linking the two when necessary.

  • What is the IORE framework mentioned in the script?

    -The IORE framework is a tool for organizing and understanding different types of applications in a business. It categorizes apps into core applications, satellite applications, and utility apps, helping businesses decide which apps to keep and which can be easily replaced.

  • What advice does Paco give for trying out a new app?

    -Paco advises to first try the app yourself, then share it with someone who has a global vision of the processes within the company. This approach helps in understanding the pros and cons before making a decision to switch or implement the new tool.

  • What is the 'shiny object syndrome' referred to in the discussion?

    -The 'shiny object syndrome' refers to the temptation to switch to a new productivity tool or app as soon as a fancier or seemingly better option appears, often leading to a cycle of constant change without fully utilizing the current tools.

  • What is the key takeaway from the discussion about changing productivity tools?

    -The key takeaway is that changing productivity tools should be a calculated decision based on clear advantages and understanding of the impact on workflows and team performance. It's important to be pragmatic and consider the costs and efforts involved in such a transition.

Outlines

00:00

📝 Introduction to Productivity and the Paperless Movement

The video begins with a warm welcome to a productivity session focusing on the paperless movement. The host introduces Paco, the co-founder, and discusses the topic of the month within their Inner Circle cohort, which revolves around changing apps and the considerations involved in switching project management tools. The conversation touches on the dilemma of whether to switch to a new tool even if it appears better, and the challenges of migrating workflows and onboarding team members to new tools.

05:01

🛠️ Evaluating the Need to Switch Tools

This paragraph delves into the reasons and strategies for evaluating the need to switch project management tools. The speaker shares personal experiences with various tools like Trello, ClickUp, Asana, and others, highlighting the importance of understanding one's workflow and the tool-agnostic approach. The discussion emphasizes the need to prioritize the business's core needs over the allure of new and shiny tools, and the importance of a gradual and well-thought-out transition when considering a switch.

10:01

🚀 Success Stories and Challenges with Project Management Tools

The speaker recounts specific instances where project management tools have been successfully implemented, such as using Asana in a large corporation and the subsequent switch to Trello. The challenges of migrating thousands of tasks and the impact on team performance are discussed. The paragraph also touches on the speaker's own experiences with different tools and the evolution of these tools over time, emphasizing the balance between sticking with a reliable tool and the potential benefits of exploring new options.

15:02

🧩 Navigating the Transition Between Tools

This section focuses on the practical aspects of transitioning between tools. The speaker describes the process of testing new tools in a 'playground' mode, the importance of having a core set of features, and the need for a direct comparison between old and new tools. The paragraph also addresses the challenges of managing the transition, especially in large teams, and the potential costs and trade-offs involved in abandoning a reliable tool for a new one.

20:03

📈 Final Thoughts on Tool Selection and Evolution

The video concludes with a reflection on the importance of understanding the different types of applications within a business, such as core, satellite, and utility apps, and the implications for tool selection and evolution. The speaker advises on using the iore framework to assess the current tool stack and make informed decisions about when and how to switch tools. The conversation ends with a reminder of the complexities involved in changing tools for a company versus an individual, and the need for a careful and strategic approach.

Mindmap

Keywords

💡Productivity

Productivity in the context of the video refers to the efficiency and effectiveness with which tasks and projects are managed and completed. It is the central theme of the discussion, focusing on how to optimize workflow and tool usage to improve overall performance in business and personal endeavors. The video explores this concept through the lens of project management tools and the decision-making process behind switching or maintaining certain tools.

💡Paperless Movement

The Paperless Movement is a concept or initiative aimed at reducing the use of paper in favor of digital alternatives, promoting a more sustainable and efficient way of managing information and tasks. In the video, this movement is likely the foundation of the discussion on digital productivity tools and their impact on streamlining business processes.

💡Project Management Tools

Project management tools are software applications designed to help teams plan, coordinate, and track projects, often including features like task assignment, progress tracking, and collaboration. In the video, the discussion revolves around the pros and cons of different project management tools like Trello, ClickUp, and Asana, and the considerations for switching between them.

💡Workflows

Workflows are the defined processes or sequences of steps taken to complete a task or project. They are crucial in productivity discussions as they outline the most efficient way to manage and execute work. The video emphasizes the importance of understanding and optimizing workflows, regardless of the specific tool used.

💡Shiny Object Syndrome

Shiny Object Syndrome is a term used to describe the phenomenon where individuals become easily distracted by new, attractive tools or technologies, often leading to frequent changes in the tools they use without fully utilizing the potential of their current tools. The video addresses this issue as a common temptation in the context of productivity tool usage.

💡Migration

In the context of the video, migration refers to the process of transferring data and workflows from one project management tool to another. It involves considerations of cost, effort, and potential disruptions to productivity, making it a significant decision for businesses and individuals.

💡Tool Agnostic

Being tool agnostic means focusing on the underlying processes and workflows rather than being tied to a specific software application. This approach allows for flexibility in choosing the best tool for the job without being limited by brand loyalty or specific features.

💡Inner Circle

The Inner Circle, as mentioned in the video, likely refers to a group of individuals or a community within the Paperless Movement who share insights, experiences, and support each other in their journey towards improved productivity. It is a term that suggests a close-knit, exclusive group focused on specific topics or challenges.

💡Onboarding

Onboarding in the context of the video refers to the process of introducing and integrating new team members or users into a particular productivity tool or system. It involves training and familiarization to ensure that users can effectively utilize the tool and contribute to the team's productivity.

💡Performance

Performance in this context relates to the effectiveness and efficiency with which a tool or system operates, often measured by the successful completion of tasks and projects. The video emphasizes the importance of maintaining high performance through stable and reliable tools, even if they may not have the latest features.

💡Advantage

In the video, advantage refers to the benefits or improvements that a new tool or system can bring over the existing one. It is a critical factor in deciding whether to switch productivity tools, as the potential benefits must outweigh the costs and efforts involved in the transition.

Highlights

The discussion revolves around the dilemma of when to switch project management tools and the associated costs and efforts.

The paperless movement co-founder shares insights on the challenges of migrating between Trello and ClickUp.

The importance of understanding tool-agnostic workflows is emphasized for smooth transitions between different productivity apps.

The presenter's experience with a 60-person team using an older project management tool highlights the risks of sticking with outdated technology.

The presenter's company has successfully managed over 500,000 tasks using their current project management tool.

The concept of 'shiny object syndrome' is introduced, where the allure of new productivity tools can lead to frequent, potentially disruptive changes.

The presenter advocates for a pragmatic approach to tool adoption, only switching when there is a clear and significant advantage.

The story of how the presenter's team transitioned from using no project management tool to successfully implementing Asana.

The challenges of migrating a large team to a new project management tool, such as the switch from Asana to Trello in a corporate environment.

The presenter's strategy for testing new tools involves a personal trial period followed by a gradual rollout within the team.

The importance of having a solid core set of tools and understanding which tools can be easily replaced or enhanced with 'satellite apps'.

The presenter's experience with an established tool, Intervals, which has been consistently improved over 15 years.

The comparison between Asana and ClickUp, with Asana being likened to Apple in its slow, deliberate feature updates.

The risks associated with betting on younger, less established tools that may require frequent workflow adjustments.

The presenter's advice on using the IORE framework to assess the importance of different apps and tools in a business workflow.

The presenter's cautionary tale about the potential downsides of switching tools, including the opportunity cost and the impact on team productivity.

The value of having a tool that has evolved over time and continues to improve, even if it's not the most 'fancy' or feature-rich option.

The presenter's approach to testing new tools in a 'playground' area to assess their potential impact on the business before full implementation.

Transcripts

play00:00

all right everybody welcome back to

play00:01

another productivity like a pro session

play00:03

here with my dear friend Paco our

play00:06

co-founder of the paperless movement and

play00:08

today we will dive into a very

play00:10

interesting topic as usual paperless

play00:13

movement your productivity your way what

play00:16

is it about today Paco well it was about

play00:19

something that emerged in our cohort the

play00:22

Inner Circle cohort that we are handling

play00:24

the this month well every month okay

play00:26

every month we will have one different

play00:28

cohort and the point and the topic was

play00:30

about changing apps one of our members

play00:33

was hesitating between moving his

play00:36

project management tool from one to

play00:38

another I think he was doing quite a few

play00:40

things in Trello I guess I'm not sure

play00:42

right now well yeah he was running

play00:44

everything in Trello actually multiple

play00:46

businesses and then he started to

play00:48

implement clickup and migrating and

play00:51

everything at once and this brought up

play00:53

the discussion about when should you

play00:55

actually switch tools over the effort

play00:58

and the cost that are in evolved and

play01:00

then when you look at this from a

play01:02

different perspective maybe you don't

play01:03

even change it even if the other tool is

play01:06

better and well we saw there Trello and

play01:09

clickup and obviously when you hear

play01:11

these two words then you instantly think

play01:14

well I'm going for clickup but who is

play01:15

using Trello anyway today it might be

play01:17

not the case in many businesses as

play01:20

Trello is very simplistic and easy to

play01:23

understand for many people and easier to

play01:26

handle so many people are used to Trello

play01:28

or kban boards and and therefore it

play01:31

might be easier to handle so migrating

play01:34

not only to a different tool but also

play01:37

workflows and people onboarding to other

play01:40

tools this is really the topic that we

play01:43

want to talk about today when you should

play01:45

do this but it also applies to your

play01:47

personal tool usage so when should you

play01:49

switch any tool overall I mean by the

play01:52

things that we will discuss today you

play01:54

will see this from a different

play01:55

perspective and it also goes along with

play01:57

the topic shiny object syndrome you you

play02:00

see a fancy trailer a YouTuber talking

play02:02

about a new productivity tool and you

play02:04

say man this is the one and only tool

play02:06

that I need now and you instantly start

play02:09

switching and then you well that's what

play02:11

we want to dive into today yes because

play02:13

there's a fear and I'm the first about

play02:16

that fear and it's the sensation of

play02:19

being behind that you are not taking

play02:21

advantage of a certain technology or a

play02:23

tool that you are using or a stick to

play02:26

the same tools so that you are not

play02:28

evolving well in my opinion it's quite

play02:31

dangerous especially when you are

play02:33

dealing with a lot of users in my case

play02:35

for instance we are more than 60 people

play02:37

in one of the companies and for instance

play02:39

we keep using a project management tool

play02:41

that I've always said that it works

play02:44

perfectly it's quite old it was a bet I

play02:47

made I think over 15 years ago so you

play02:50

can imagine the technology at that time

play02:52

and well they have been keep evolving

play02:54

and if you compare this tool with the

play02:56

current project managers like aana or

play02:59

clickup or or linear well if you compare

play03:01

it with linear man what a difference but

play03:03

the point is that it works perfectly

play03:07

okay all the workflows work without any

play03:09

problem everybody knows what needs to be

play03:12

done we are able to prioritize we use it

play03:15

as a communication tool so we don't use

play03:17

email talking about task related to

play03:19

projects and the thing is well we are

play03:21

also registering our recording Sor are

play03:24

ours that we dedicate to the different

play03:26

projects and well pretty easy the the

play03:29

app name

play03:30

that okay because there's aial it's

play03:33

quite unknown because in fact the thing

play03:36

that I love the most about this app it

play03:38

was the database model behind the tool

play03:41

because I saw that the different

play03:42

entities the objects the relationships

play03:45

between them the links how everything

play03:47

was pretty well implemented and I think

play03:49

that the success of any tool we are

play03:52

seeing like some of the tools like for

play03:53

instance to do is is leveraging thanks

play03:56

to have that amazing database model that

play03:58

allows them to connect anything to

play04:01

leverage to create new features without

play04:04

affecting the foundational core and

play04:07

really fast and this applications for

play04:09

instance has been well improving little

play04:11

by little it's something that is not

play04:13

something fancy it's not something

play04:15

horrendus okay I have to say that too

play04:17

but the point is that I will never try

play04:19

to change it unless I clearly see that

play04:23

there's a clear Advantage okay without

play04:25

any hesitation because I have to say

play04:27

something at the beginning without using

play04:29

a tool it seems that everything is going

play04:31

to work pretty well and the moment that

play04:33

you go really deep into that tool you

play04:35

see the weaknesses that any other tools

play04:38

has so beware that's the thing that I

play04:40

say and the question is now well

play04:43

obviously the question arises what is

play04:45

this tool and what is the name and you

play04:47

said intervals but now is the question

play04:49

would you recommend it to somebody who

play04:51

is just starting a new business now I

play04:53

mean in this case it would be for a

play04:55

marketing agency right it depends on the

play04:58

use case for me it's something that it's

play05:00

a tool really easy to understand so if

play05:03

you have many uses I do think that it's

play05:06

a a good bet it's just a matter of

play05:08

giving it a try and see if it worked but

play05:10

if you try to compare it with any of

play05:13

this project management tool the the

play05:15

current that I have mentioned that you

play05:17

can find and are the big players like

play05:19

well even Monday I forgot about Monday

play05:21

for instance I have to say I have tried

play05:23

all of them okay I have try Asana and I

play05:25

currently using clickup I'm currently

play05:28

using linear I have used Monday in the

play05:30

past I think I have used most of the big

play05:32

players talking about well Trello was

play05:34

something that never worked for me it

play05:36

was too simple and for me there's a

play05:38

moment that Canan boards don't work if

play05:40

you have a high volume of information

play05:43

and the point is that most of these

play05:44

tools even intervals you can see the

play05:47

information in C Bo you can do that in

play05:49

Monday well in many of the project

play05:51

management tool you can do it so well

play05:52

it's a feature that even some of that

play05:54

are not so board-based I would say they

play05:57

are currently using it so well why not

play06:00

for me it's simple it works it's a

play06:03

company that it's really well

play06:04

Consolidated because in fact as usually

play06:06

happens it was a software company okay

play06:08

who didn't find out the correct project

play06:10

management tool and then they decided to

play06:13

create their own tool and well it worked

play06:15

so well for them that they started to to

play06:17

sell it and well in fact they've been

play06:19

doing it I thought and it was one of my

play06:21

biggest fear in that it was going to

play06:24

disappear but it never disappear and

play06:26

they kept running the business and they

play06:29

kept improving it and they also improve

play06:31

the onboarding process and well you can

play06:34

handle many things using that tool but I

play06:37

could say that it looks like all the

play06:38

style I could say it works at the end I

play06:41

am pragmatic and it's a tool that I've

play06:43

been using it I think that the last year

play06:46

we handle more than 500,000 tasks so you

play06:49

can imagine the the volume of this tool

play06:51

without any problem I mean the database

play06:53

behind it's really welld developed and

play06:55

that's why you don't have any

play06:57

performance issues for instance that's

play06:59

important when you are talking about big

play07:01

okay quote 60 people team but well it's

play07:04

quite quite a white people especially if

play07:06

you pay the salaries every month and the

play07:08

point well it's one of the tool and

play07:09

that's why I cannot move it has to be

play07:13

something so lifechanging for instance

play07:14

and really looking forward right now to

play07:17

an amazing tool to record the hours of

play07:20

the team much easily using AI using

play07:23

recommendation using historical data so

play07:26

people can't record their hours because

play07:29

of the talking about the profit of each

play07:31

project each client well a much more

play07:33

complex tool that it's link to the

play07:35

financial system and that's why I've

play07:38

been always looking and in fact right

play07:40

now I'm trying to look for another tool

play07:43

but at the moment I haven't changed it

play07:45

for these big players that I've just

play07:47

mentioned yeah and Ariel just says how

play07:49

do you try an app is it not a quite

play07:52

complex issue and that's exactly what it

play07:54

is trying an app or especially with the

play07:57

team and when should you do this so I

play07:59

would tell a bit of a about my backstory

play08:01

there when I was part of a team in big

play08:04

corporate I was advocating always new

play08:06

tools and improved team performance and

play08:08

there was a struggle in the beginning

play08:10

because we instantly implemented new

play08:12

tools in the team and everybody had to

play08:14

start to using that but not everybody is

play08:16

a fan of switching tools and then they

play08:19

have Daily Business to do and this is

play08:21

where the first learning I mean we are

play08:23

talking from more than 10 years ago

play08:25

there I started to use them myself along

play08:28

with the exist tools but there what key

play08:31

is you have to understand the tool

play08:33

agnostic workflows first and that's what

play08:36

where iore comes into play when you go

play08:38

through arel you just joined the Payless

play08:40

movement well you just joined the

play08:41

Payless movement membership so welcome

play08:42

to the party when you go through the

play08:44

iord Journey now you will get the

play08:47

understanding of the tool agnostic

play08:49

Concepts and workflows in productivity

play08:51

end to end from information collection

play08:53

and management to also project

play08:55

management task management and so on to

play08:57

the action world and this is really key

play09:00

that's why we are so forcing the things

play09:02

into the tool agnostic space even though

play09:04

that we are providing implementation

play09:07

examples how we Implement these Concepts

play09:09

and workflows to the tools that we use

play09:11

ourselves to better explain how they

play09:13

work in real life but key is to

play09:16

understand the workflows in your

play09:18

business in the tools that you're

play09:19

currently using if you don't have any

play09:21

workflows or you don't recognize them

play09:23

this is the moment where you start to

play09:25

write them out to understand them

play09:27

because then you can instantly switch to

play09:30

different tools because the underlaying

play09:32

workflows will just work in any other

play09:34

tool you will realize and that's why we

play09:36

say that you will realize when you go to

play09:38

Monday assana clickup intervals I don't

play09:41

care I'm not even scared opening any

play09:44

other tool up because there will be

play09:45

always a basic set of features that

play09:48

every project manager provides and then

play09:50

you will have the understanding what

play09:52

features you really need to run your

play09:54

business and therefore one tool provides

play09:57

more features in One Direction and

play09:59

another tool provides features in a

play10:00

different direction and therefore you

play10:02

start to understand what is really

play10:04

helping you so getting back to my

play10:06

example I was taking over a team was a

play10:09

team leader myself and they had no

play10:11

project management tool at all and I was

play10:14

working in a 300,000 employee company

play10:16

and there was obviously a lot of

play10:18

actually human project managers right

play10:20

they had their tools and we were working

play10:23

in several projects and I came into this

play10:25

team and I used aana back then as the

play10:28

first tool for myself just to collect

play10:31

projects that my team is working on

play10:33

because they were firefighters they had

play10:35

no idea so we had to get some structure

play10:37

and therefore I was collecting all the

play10:39

projects that these been working on and

play10:41

they were working on 150 projects in

play10:43

parallel with five people globally and

play10:46

that's where I had them already listed

play10:47

all in assana and therefore I was able

play10:50

then to go to the manager and and show

play10:52

him well these are all the projects we

play10:54

are working on there are too many now

play10:55

you see them listed out so we were able

play10:58

to prioritize the projects that we

play10:59

really need to focus on so we narrowed

play11:02

it down to 50 projects and then I

play11:04

onboarded the team slowly to assana

play11:06

because this became each project in

play11:09

assana became a single source of Truth

play11:11

for this project so we started to

play11:13

collecting information on this project

play11:15

and this is where the team then learned

play11:17

the advantage of having one tool where

play11:20

they know when they go there they will

play11:21

find all the information in Need for

play11:23

this project instead of somebody calling

play11:25

you about the project and then you start

play11:27

searching for the information from all

play11:28

the different sources and uh while this

play11:31

became so successful that we also got a

play11:34

different department in the engineering

play11:36

department and we worked together in the

play11:37

same tool cross Department wise and then

play11:40

we rolled out Asana for more than a

play11:42

thousand people globally all working in

play11:44

Asana and well we came up to 16,000

play11:47

tasks handling per month within just

play11:50

half a year and now we come to the topic

play11:52

of this podcast we were running this

play11:54

assana it was very successful the team

play11:57

performance increased by 40% cross C

play11:59

Department performance and suddenly the

play12:01

company decides that Trello becomes the

play12:04

official project management tool for the

play12:06

whole company 300,000 employees and we

play12:08

have to kill aana and actually I was

play12:11

working in it and I was a business

play12:12

analyst and it was my job to explain

play12:15

exactly when we should switch tools and

play12:18

so I get a request from the management

play12:20

well you have to kill asan you have to

play12:21

use Trello now and I just make a simple

play12:23

calculation how much it would cost to

play12:26

stop the projects that we are working on

play12:28

right now to migrate data over 16,000

play12:30

tasks to the new project to onboard the

play12:33

thousand people to these new workflows

play12:35

in Trello because Trello had less

play12:37

features than aana therefore we were

play12:39

leveraging a lot more so we had to work

play12:41

do workarounds so we've been talking

play12:43

about a million about a million euros

play12:45

for the migration process itself just to

play12:48

go to a tool that they say we should use

play12:50

and therefore this number when they see

play12:53

costs versus the force that you have to

play12:55

go over then we stopped it we were able

play12:58

to keep using Asana on the other hand we

play13:01

always were forcing the things that we

play13:03

all using the same tool because it makes

play13:05

it so much easier to use this so to

play13:07

overcome this we had to use Trello in

play13:10

parallel and therefore in Trello

play13:12

whenever a project manager was in Trello

play13:14

we were linking out to the relevant

play13:16

tasks in assana and that's always key so

play13:19

you're always able to build up systems

play13:22

in parallel and then have at least the

play13:24

links to the relevant content in one

play13:27

Major Tool and that's the same that we

play13:29

said to our Inner Circle member in this

play13:31

coaching session where he should slow

play13:34

down with the migration process as he

play13:36

was talking about I don't know 160

play13:38

people something migrating to a new an

play13:41

API to an AP well there was there was

play13:45

another there was another in member

play13:47

trying to migrate from Monday to clickup

play13:49

that was the apis so he wanted to bring

play13:51

over dashboards but the one member with

play13:54

Trello and click up so he partially

play13:56

migrated and was the right process

play13:58

migrated just one Department was the

play14:00

marketing department starting in clickup

play14:02

and therefore it needs really to be

play14:04

siloed so they have really their

play14:06

processes in their Department it's not

play14:08

affecting the other departments so it's

play14:10

a big step to really switch tools and it

play14:13

really needs to have a big advantage to

play14:15

switch the tools because the moment

play14:17

where you get excited about oh man when

play14:20

we are in there in your brain it looks

play14:22

so fancy everything and it makes all the

play14:24

sense that you use this new tool but the

play14:26

moment you go to the new tool this is

play14:28

where then after one two months you

play14:30

realize man it's not so much better than

play14:32

the other one but the opportunity costs

play14:34

where people weren't able to focus on

play14:36

tasks not being able to work on new

play14:39

stuff this migration espe especially

play14:41

with big teams this is crazy if you just

play14:44

getting started with your business your

play14:46

solopreneur I mean this is a lot easier

play14:49

but even then I was using notion for a

play14:51

long time then I switched to click up

play14:53

then I tested all the other things

play14:54

obviously this was my chob in the side

play14:56

hustle with the paperless movement

play14:58

testing out all the project managers in

play15:00

addition to the ones that already new

play15:02

this is where I came up with the

play15:04

playground where the sent box mode where

play15:07

I just have a closed area where I say

play15:09

okay I'm testing this tool now but this

play15:11

is not part of my business I'm just

play15:13

playing and I'm just pretending that I'm

play15:16

using it and then you see the friction

play15:19

points and then you really see if it is

play15:21

worth migrating or not and even if it is

play15:23

more effort to run the tools in parallel

play15:27

it's really worth it because you have a

play15:28

direct comparison to what you have right

play15:30

now and what you could have in the other

play15:32

tool and then it makes sense to really

play15:34

look into is it worth cost investment to

play15:37

migrate over all the stuff to the new

play15:39

tool yes for me the the way to try an

play15:41

app is well I try it myself that's the

play15:44

first thing and the moment that I'm more

play15:46

or less convinced then I have one person

play15:48

in the company that has a global vision

play15:50

of the processes because she's in the

play15:53

middle of everything and then I share it

play15:55

with her and we theci side okay we see

play15:58

the pros and cons and the point is that

play16:01

most of the tools are rejected by us

play16:05

okay no matter how different they may

play16:07

seem or how they crucial or that we are

play16:10

missing something by not using these new

play16:13

tools because it's really tough it's

play16:15

really tough when you have to handle

play16:17

with the people's frustration all the

play16:19

trade-offs of people wasting their times

play16:22

people getting angry because they cannot

play16:24

work comfortable too many things that at

play16:26

the end at the end and also this shows

play16:29

that when you have Consolidated

play16:30

workflows that they have been working

play16:32

pretty well in a complex system as a

play16:35

business is you don't need to reinvent a

play16:37

whe constantly you know it's much better

play16:39

to stay and bet on good tools that even

play16:43

you see this is not one of the big

play16:45

players in the market of project

play16:46

management but even this tool is

play16:48

evolving is progressing because I have

play16:50

to say for during this 15 years it has

play16:53

evolved okay and and the team with with

play16:56

them they have been introducing new

play16:57

features they have been improving they

play17:00

are constantly well improving the things

play17:02

so why not having maybe it's not so

play17:04

fancy or maybe we are lacking some of

play17:07

the features for instance talking about

play17:08

Knowledge Management is not a tool at

play17:11

all okay you cannot compare with those

play17:13

project management like ca where you can

play17:15

perfectly combine the bkm area and the

play17:17

area bkm and BPM bkm and BPM okay I mean

play17:21

the project management and the knowledge

play17:23

management related to business but well

play17:26

it doesn't matter okay behind for be we

play17:29

have some of the tools like for instance

play17:31

Google Docs okay and all the power of

play17:34

Google behind so we just put the link in

play17:37

that project management and everything

play17:39

is connected and also we are building a

play17:41

huge Knowledge Management database based

play17:43

on on another tool that I always forget

play17:46

the name strip I think because I'm

play17:49

always confused with stripe I think it's

play17:50

strip well it's quite famous and they

play17:52

are making an amazing job talking about

play17:55

Knowledge Management for companies and

play17:57

well we are getting and covering those

play17:59

gaps but the core element you know the

play18:02

action the getting things done for the

play18:03

company especially with that high volume

play18:06

of data is well preserved we are really

play18:08

happy people are happy although many of

play18:11

them complain because they want more

play18:13

futuristic tools okay but at the end

play18:16

it's much better for the company to stay

play18:18

on the things that you know than those

play18:20

one who may be better at the beginning

play18:22

but the moment that you start using them

play18:25

daily and with high volume of data it's

play18:27

something that sometimes you have

play18:30

surprises and that's something that I

play18:32

have well especially about performance

play18:34

it's something that you never should

play18:36

take for granted because when you are

play18:38

dealing with a huge amount of data is

play18:41

not the same with for instance when

play18:42

you're in a testing Zone okay with

play18:44

yourself just one project that you take

play18:46

as a test and things like that when you

play18:48

start uploading the things and a lot of

play18:51

recurring uses for instance too it's not

play18:53

just a matter of the database model but

play18:55

also the servers the well too many

play18:58

technical aspects that when a huge

play19:01

company is working daily without any

play19:03

problem changing that a step forward

play19:06

should be huge okay to justify that move

play19:10

because the tradeoff and the suffering

play19:12

of the transition is horrendous

play19:14

horrendous right now I'm an and this is

play19:17

being well it's knocking me down for one

play19:19

year and even three years before that we

play19:21

were preparing everything well it's a a

play19:24

mess a mess when you are dealing with

play19:26

complicated systems the thing is also so

play19:29

that you bet on intervals makes also

play19:31

sense with a 15-year established tool

play19:33

and they keep improving the things they

play19:35

make probably slow steps because they're

play19:37

careful not to destroying all the setups

play19:39

for from their customers if you compare

play19:42

it to something like clickup that is

play19:44

fairly young company and now they made a

play19:47

switch from clickup 2.0 to 3.0 and if

play19:50

you go to the forums people are really

play19:52

complaining because all the workflows

play19:55

need to be Rewritten how to go to the

play19:57

inbox where they Pro process Sops that

play20:00

they established already so for clickup

play20:02

it was the right decision to get to this

play20:04

next level that was important they had

play20:06

to do it but if you bet on a young tool

play20:08

you have to expect these changes right

play20:11

that's the thing and how crucial this is

play20:13

so that's why I compared always Asana

play20:16

and clickup being Asana the apple and

play20:18

clickup more the Android thing where

play20:21

Apple also makes very slow changes it's

play20:24

very small changes but then if they

play20:26

Implement something it makes sense and

play20:28

the overall concept of the tool and

play20:30

that's what you see in aana it is also

play20:33

of one of the very established tools

play20:35

since when they launch also more than 10

play20:38

years or maybe even 15 years ago already

play20:40

I remember that that was the first one

play20:42

that we used back then and we wi labeled

play20:45

it for the big company and they had all

play20:47

these things as well that you were able

play20:50

to Wi label this for big companies and

play20:52

they were targeted towards big companies

play20:54

so they cannot afford to really make

play20:57

fancy changes in there there that

play20:59

interrupts everything or introduces bugs

play21:02

because as you mentioned imagine that

play21:04

the project manager stops working for

play21:06

one week the whole business just stops

play21:08

working that's the that's really the

play21:10

issue and where you really have to be

play21:12

careful with all these fancy new tools

play21:14

coming out and saying well we are the

play21:16

next clickup we are better than clickup

play21:18

and better than notion and so on if you

play21:21

are solar preneur starting out you can

play21:22

bet on these things and maybe you don't

play21:25

have so many tasks but once you as pako

play21:28

says with 500,000 tasks imagine you go

play21:30

to a tool that you don't know the future

play21:32

of and maybe it disappears in one year

play21:34

from now this is just impossible for the

play21:37

bigger companies and this is why the

play21:39

established tools bet on the big

play21:41

companies and the smaller tools they

play21:43

really reach out for the entrepreneurs

play21:45

and so on and try to promote it rather

play21:47

there yes and it's also it also happens

play21:50

and it happens to me that when you have

play21:52

been using a tool for quite a long time

play21:54

you start to not to pay attention to

play21:56

certain features you think that they

play21:59

exist all over the place no matter the

play22:01

tool and it's the moment that you make

play22:04

the move when you start well remembering

play22:07

all those features that meant nothing

play22:10

for you at that moment when you were

play22:11

using your current tool and it's now

play22:13

when you have made the change when you

play22:15

start saying that it wasn't so bad your

play22:18

current application and that's something

play22:20

that it's inherent I could say to human

play22:22

beings okay that it's the moment that we

play22:24

lose something the moment that we pay

play22:26

attention to that no and the moment that

play22:28

we have it we don't pay any attention at

play22:30

all so be careful and uh well that

play22:33

doesn't mean that you don't evolve okay

play22:35

we are constantly evolving but the pace

play22:37

for a company is not the same as an

play22:40

individual because it's impossible okay

play22:41

because the complexity has nothing to do

play22:44

and well one thing is well I'm going to

play22:45

change my task manager for me and

play22:47

another thing is I'm going to change the

play22:49

the project management of a whole

play22:51

company that's totally different and the

play22:52

approach should be totally different and

play22:55

that's where the Ia framework comes into

play22:57

place so for me who join you laying out

play23:00

your current tool stack on the iore

play23:02

framework and there you learn the

play23:04

difference between core applications

play23:06

satellite applications and utility apps

play23:09

so the core applications usually are

play23:12

your project managers the no taking apps

play23:14

where you have your P Gams in there and

play23:16

they should be very rarely changed and

play23:19

satellite apps are just enhancing your

play23:21

existing core apps and therefore they're

play23:23

easy to exchange so if this is something

play23:25

you're interested in and you haven't

play23:26

done already your IO framework do this

play23:29

first because then you will very quickly

play23:31

realize what is really your important

play23:33

apps in your business that you should

play23:35

keep running as long as possible and

play23:37

which one could you replace very easily

play23:39

with other tools so well I think that

play23:42

was it about the session everything that

play23:44

needed to be said res said and if not

play23:47

then let us know we are happy to follow

play23:49

up in the next live Q&A so until then

play23:51

catch you up in the next one okay see

play23:53

you guys bye-bye

Rate This

5.0 / 5 (0 votes)

Related Tags
ProductivityTipsProjectManagementToolSwitchingTrelloClickUpWorkflowOptimizationBusinessGrowthTechAdoptionInnerCircleShinyObjectSyndrome