The Future of Work: How AI May Create New Jobs and Opportunities

As we move with all speed into the era of artificial intelligence (AI), some may worry about the impact this technology will have on jobs and the economy. However, I am optimistic about the potential of AI to create new jobs and opportunities soon. While some jobs can be automated, people will always be needed to design, build, and maintain these systems. In this article, we explore potential works and opportunities that AI has the potential to create, as well as the skills and experience that will be in demand in this new era of AI.

The field of artificial intelligence (AI) has made significant progress in recent years, and it is transforming the way we live and work. While some are concerned about the potential impact of AI on jobs and the economy, many experts believe that AI will ultimately create new jobs and opportunities, rather than replace them. In this article, we will explore some of the potential jobs and opportunities that AI may create in the future.

01 |    AI trainers and explainers

As AI systems become more advanced, there will be a need for professionals who can train and explain these systems to others. AI trainers and explainers may help to design, build, and maintain AI systems, as well as train others to use them effectively. This job is likely to require expertise in areas such as machine learning, natural language processing, and computer science.

02 |    Data analysts and scientists

With the vast amount of data that is generated every day, there is an increasing need for professionals who can analyze and make sense of this data. AI can help to automate some aspects of data analysis, but there will still be a need for humans to interpret and make decisions based on the results. Data analysts and scientists may work in a variety of industries, including healthcare, finance, and technology.

03 |    Cybersecurity experts

As AI becomes more prevalent, there will be an increasing need for professionals who can ensure that these systems are secure and protected from cyber-attacks. Cybersecurity experts may work on developing new AI systems that are more resilient to attacks, or they may focus on securing existing systems from potential threats. This job is likely to require expertise in areas such as cryptography, network security, and risk management.

04 |    Customer experience specialists

AI has the potential to revolutionize customer experience, and there will be a need for professionals who can help to design and implement these systems. Customer experience specialists may work on chatbots, voice assistants, and other AI-driven tools that help to improve customer service. This job is likely to require expertise in areas such as user experience design, product management, and marketing.

05 |    Ethical and legal experts

As AI becomes more advanced, there will be a need for experts who can ensure that these systems are used ethically and legally. This may involve developing new regulations and laws, as well as ensuring that AI systems are designed and used in a responsible manner. Ethical and legal experts may work in a variety of industries, including healthcare, finance, and government.

06 |    AI-assisted creatives

While AI is not yet capable of true creativity, it can be used to assist creatives in a variety of fields. For example, AI can be used to generate music, art, and literature, which can then be refined and improved upon by human creatives. AI-assisted creatives may work in industries such as advertising, entertainment, and publishing.

07 |    Personalized healthcare professionals

AI has the potential to transform the field of healthcare by enabling personalized treatments based on individual patient data. Personalized healthcare professionals may work on developing AI systems that can analyze patient data and provide personalized treatment recommendations. This job is likely to require expertise in areas such as machine learning, bioinformatics, and medicine.

These are just a few examples of the many jobs and opportunities that AI may create in the future. As AI continues to evolve, it is likely that new jobs and industries will emerge that we cannot even imagine today. While there are concerns about the potential impact of AI on jobs and the economy, it is important to remember that AI is ultimately a tool that can be used to augment and enhance human capabilities, not to replace them.

Note: This article was written by Ibrahim Maro with a little help from ChatGPT AI. We may have different writing styles and perspectives, but we both agree that the potential of AI to create new jobs and opportunities is worth exploring. And don't worry, no AI was harmed in the making of this article! 😁😎

The Impact of Platform Thinking on Business Analysis

In recent years, the rise of digital transformation has brought about a new way of thinking in the business world, known as platform thinking. Platform thinking refers to the development of digital platforms that offer a range of products, services, and experiences to customers. This shift has had a significant impact on business analysis, as traditional business models are being challenged by this new way of operating. In this article, we will explore the impact of platform thinking on business analysis and the benefits of adopting an agile methodology.

Business analysis is a critical discipline that involves understanding the needs of stakeholders, identifying opportunities for improvement, and defining solutions to business problems. In the past, business analysts would work on projects in isolation, analyzing data, and presenting recommendations to decision-makers. However, with the rise of platform thinking, this has changed dramatically. Business analysts now play a key role in defining and building digital platforms that provide a wide range of products and services to customers. They are responsible for understanding the needs of stakeholders and defining the features and functionality of the platform that will best meet those needs.

One of the biggest challenges faced by business analysts in the world of platform thinking is the need to work across multiple departments and teams. In a traditional business model, a business analyst might work only with the IT department. However, in a platform-based business, they must collaborate with teams such as marketing, product development, and customer service to ensure that the platform meets the needs of all stakeholders. This requires business analysts to have a broader skill set, including communication and collaboration skills, to ensure that everyone is aligned on the goals of the platform.

Another challenge faced by business analysts in a platform-based business is the need to work in an agile environment. Agile is a project management methodology that emphasizes collaboration, flexibility, and continuous improvement. It is designed to help teams respond quickly to changes in the market and to deliver value to customers in short cycles. In the world of platform thinking, business analysts must be able to work in an agile environment, as the platform is constantly evolving based on customer feedback and market trends.

Despite these challenges, there are several benefits to adopting platform thinking and an agile methodology in business analysis. One of the biggest benefits is the ability to deliver value to customers more quickly. In a platform-based business, business analysts work in short cycles, delivering new features and functionality to customers on a regular basis. This allows businesses to respond quickly to changes in the market and to meet the needs of customers in real time.

Another benefit of platform thinking and agile methodology is the ability to collaborate effectively across teams. By working in an agile environment, business analysts are able to work closely with other teams, including product development, marketing, and customer service, to ensure that the platform meets the needs of all stakeholders. This leads to a better understanding of customer needs and more effective solutions to business problems.

In conclusion, platform thinking has had a significant impact on business analysis. Business analysts now play a key role in defining and building digital platforms that provide a wide range of products and services to customers. While there are challenges to working in a platform-based business, such as the need to work across multiple departments and in an agile environment, there are also many benefits, including the ability to deliver value to customers more quickly and to collaborate effectively across teams. By embracing platform thinking and an agile methodology, businesses can stay ahead of the curve and continue to meet the evolving needs of customers.

 

Tips for Writing Effective User Stories

What is the User Story, anyway?

User stories are brief descriptions of a feature or functionality from the perspective of an end user. 

They are often used in agile software development to capture requirements and guide the development process. 

Here are a few quick tips for writing effective user stories:

Keep it simple

Keeping user stories simple and easy to understand is important because it helps to ensure that they are clear and well-defined. 

Using plain language and avoiding technical jargon can help make the user story more accessible and easier to understand for everyone involved in the project. 

This includes end users, business analysts, and developers. By using simple, clear language, you can help ensure that the user story accurately communicates the feature or functionality being described, and that it can be understood by all stakeholders.

Focus on the user's perspective

Focusing on the user's perspective is important because it helps to ensure that the user story is centered on the needs and goals of the end user. 

By describing the value or benefit that the feature will provide to the end user, you can help ensure that the user story is focused on delivering value to the user, rather than simply describing a technical feature or functionality. 

This can help to ensure that the feature or functionality being developed is aligned with the needs and expectations of the user, and that it will be useful and meaningful to them.

Make it specific

It's important to make user stories specific because it helps to ensure that they are clear and well-defined. 

A specific user story describes a particular feature or functionality in detail, rather than a broad or general concept. This can help to ensure that the user story is actionable and can be understood by all stakeholders. 

A specific user story should include enough detail to provide a clear understanding of what the feature or functionality is, how it will be used, and what value it will provide to the end user. This can help to ensure that the user story is accurate and realistic, and that it can be effectively implemented by the development team.

Include acceptance criteria

Acceptance criteria are specific, objective criteria that must be met in order for a user story to be considered complete. 

They are used to define the boundaries of the user story and to provide clear, objective criteria for determining when the user story is done. 

By including acceptance criteria in a user story, you can help ensure that the user story is clear and well-defined, and that there is a shared understanding among all stakeholders about what needs to be done in order to consider the user story complete. 

This can help to ensure that the user story is accurately implemented and meets the needs and expectations of the end user.

Use the "As a [user], I want [feature] so that [benefit]" format

The "As a [user], I want [feature] so that [benefit]" format is a common way of writing user stories, and it can be a helpful way to clearly define the user, the feature, and the benefit. 

This format helps to ensure that the user story is focused on the user's perspective and the value or benefit that the feature will provide. By using this format, you can help to ensure that the user story is easy to understand and provides a clear understanding of what the feature or functionality is, who it is intended for, and why it is important. 

This can help to ensure that the user story is accurate and realistic, and that it aligns with the needs and goals of the end user.

Involve the right stakeholders

It's important to involve relevant stakeholders, such as end users, business analysts, and developers, in the process of writing user stories. This can help ensure that the stories are accurate and realistic, and that they align with the goals and needs of the project. 

By including end users, business analysts, and developers in the process, you can gather a diverse range of perspectives and input that can help to ensure that the user stories are well-rounded and effective. This can also help to build consensus and alignment among all stakeholders, which can be beneficial for the success of the project.

Use examples and scenarios

Including examples and scenarios can be a helpful way to clarify user stories and provide context for the feature or functionality being described. 

Examples and scenarios can help to illustrate how the feature or functionality will be used in practice, and can provide concrete examples of the value or benefit that it will provide to the end user. This can help to ensure that the user story is easy to understand and that it accurately communicates the intended functionality. 

Examples and scenarios can also be useful for helping stakeholders to understand the context in which the feature or functionality will be used, which can be helpful for prioritization and planning.

Keep it small

Keeping user stories small and manageable is important because it helps to ensure that the development team can make steady progress and deliver value incrementally. 

By keeping user stories small, you can help to ensure that they are easy to understand and that they can be completed in a short time frame. This can help to keep the project on track and ensure that the development team is able to deliver value on a regular basis. 

Additionally, by delivering value incrementally, you can help to ensure that the project remains aligned with the needs and goals of the end user, and that it can adapt to changing requirements or priorities as needed.

Use story points to estimate effort

Story points are a relative measure of complexity and effort that are used to estimate the effort required to complete a user story. 

They are typically used in agile software development to help the development team prioritize and plan their work effectively. By assigning story points to user stories, the development team can get a sense of the relative complexity and effort required to complete each story, which can be helpful for planning and estimation purposes. 

Story points are usually assigned using a scale, such as the Fibonacci scale (1, 2, 3, 5, 8, 13, etc.), which allows for a broad range of complexity levels to be captured. The use of story points can help the development team to better understand the work required to complete user stories, and to plan and prioritize their work accordingly.

Use a user story template

Using a user story template can be a helpful way to ensure that all the necessary information is included in the story. 

A user story template typically includes the user, the feature, and the benefit, as well as acceptance criteria and any additional notes or comments. By using a template, you can help to ensure that all the key information is captured in a consistent and organized manner, which can be helpful for ensuring the clarity and completeness of the user story. 

A user story template can also be a useful tool for guiding the writing process and helping to ensure that all the relevant information is included. There are many different user story templates available, and you can choose the one that best fits the needs and goals of your project.

I hope these tips are helpful in writing effective user stories. 

Good luck and see you in my next blog!

It is more than a story, it changed my life.

A broken body isn't a broken person

Cross-country skier Janine Shepherd hoped for an Olympic medal — until she was hit by a truck during a training bike ride. She shares a powerful story about the human potential for recovery. Her message: you are not your body, and giving up old dreams can allow new ones to soar.

ABC of Taxonomy

Taxonomy is everywhere in our lives. Imagine how ugly a restaurant menu would be if it wasn’t classified and organized. You might spend more than 15 minutes just to decide what you’re having. Oh, and if you were a group of people with different trends and ages, it might take you half an hour to just to order your dishes.

On the other hand, a classified and organized menu will help you to order your dish quickly and happily, even with a large group of people. It is a mutual benefit for you and the restaurant, since you will get your dish faster, which means your table will be available for the next customer faster as well. Thank you “Taxonomy”.

In business, taxonomy provides a method to organize valuable documents into a structure that is easier to find and use. Wherever the documents are stored, the structure creates logical correspondences between any related collections of documents.

What is Taxonomy?

As in dictionary.com: Taxonomy 1. The science or technique of classification 2. A classification into ordered categories. It seems clear, but I prefer the knowledge management standpoint about the taxonomy. Taxonomy is classification scheme, semantic and knowledge map. Source: Organising Knowledge (Patrick Lambe, 2007)

• A classification Scheme: A means by which employees classify the important letters, memos or e-mail inboxes.
• A semantic: It is meaningful and transparent for knowledge workers within the organization. When a document is labeled 'Project Kickoff', everybody should know what kind of documents they can expect to find within that category.
• A knowledge map: Comprehensive, predictable and easy to navigate, in the course of the knowledge domain of the user covered by the taxonomy.

Nowadays, business relies more on taxonomy to store and retrieve critical information. Different businesses with different consumers and different needs form the way they apply taxonomy of Internet and Intranet. There are types of taxonomy presentation for different business cases and strategy alignment factors. Most common types are:

• Faceted taxonomy: It classifies objects using multiple taxonomies that express their different attributes or facets rather than classifying using a single taxonomy. Source: http://en.wikipedia.org/wiki/Faceted_classification

• Example: select a mobile phone based on characteristics such as region, type and price.

• Flat or List taxonomy: group content into a controlled set of categories. Alternatively, simple collection of related things.

• Example: a pull-down menu of country names or geographical regions.

• Trees taxonomy: represents a transition from general to more specific relationships or whole to part.

• Example: phone directories

• Hierarchical taxonomy: a specific tree structure that has inclusiveness, consistency, and maintains the same type of relationship at each level. The child inherits all of the characteristics of the parent and each child can only belong in one place in the taxonomy. Source: Organising Knowledge (Patrick Lambe, 2007)

• Example: Biological classification

• Network or Poly-hierarchal taxonomy: used when an item belongs to more than one place in the real world and multiple organizing principles are required. Provides “virtual linking” between hierarchies.

• Example: a single collection of content concerning diseases can be organized via affected body part and causes.

Stop! Do not mix between taxonomies and navigational taxonomy. Navigational taxonomy helps knowledge worker to organize their documents according to two main folder structures: Organizational or Functional folder structures. It is the way a document is physically organized in a repository providing just a single point of access to the document. If a document is well- attached and indexed using taxonomy, it should not matter how the document is physically listed in the repository. This type of navigational systems adds extra burdens for security and implementation.

• Organizational folder structure: representing business units (Departments, sections, units… etc.)
• Functional folder structure: representing business function (Employee files, employee payroll… etc.)

I am planning to write about taxonomy types in my next post. We will go deeply into the meaning and provide real business case examples.

So, why is Taxonomy important?

Taxonomy is a very critical aspect for today’s business. One of the most significant benefits of taxonomy is to reduce time and costs spent on discovery. Accordingly, document search and retrieval are accelerated to provide the knowledge workers with quick, consist and trustworthy information.

Departments in most organization build its own taxonomy in order to classify the documents they rely on for business processes. They always use their own vocabularies and terms that make sense to the users within the department. But, it doesn’t cross the boundaries of the single department or unit. When document moved around between departments or even among same department units, the classification will be lost.

Therefore, applying uniform taxonomy is a must to have, not nice-to-have, for these organizations in which focus is on information finding and making. It is not the only reason, but there are numerous reasons that should motivate corporations to apply taxonomy across:

• To enable users to share information on an enterprise basis.
• To provide a consistent user experience.
• To make searches more efficient.
• To enable automated capture of metadata attributes needed to classify a document.
• To organize content and aid in navigation.
• To support compliance.
• To retrieve information and clarify results.
• To facilitate collaboration
• To organize projects, processes, and other abstract items by type, topic, and other metadata.

It is time to apply Taxonomy

Before implementing taxonomy, you must plan for it. During my web search on how to getting things done, I found a very interesting 5 phases planning model called the Natural Planning Model. Source: http://facilethings.com/blog/en/basics-natural-planning

Natural Planning Model will help you acquainting your job, but you still need to consider that people is the core factor who makes the project succeed or fail. One of the most successful elements of taxonomy projects is the richness of making data about data. But, if you haven’t considered engaging expert matter people and supporting them through some kind of automation, it will not work.

Change management is a challenge and automatic taxonomy build and insertion is required. Although there are technically advanced products that can build taxonomies with little or no human involvement, completely automated solutions are not recommended for most organizations. So focus on people.

Your first step in planning is to study your company’s business strategy. And then, to find the unstructured documents relevant to the strategy and plan how the massive information could be organized and delivered in efficient way to people when they need it to accomplish their job.

Answering the below questions may help you figure out how your plan should be:

• What is the size of your organization?
• How complex are your business processes?
• What are the common goals of knowledge workers who participate in building your organization’s information?
• What types of documents or content they are creating? And where and how is it stored and retrieved?
• What are the common vocabulary terms used within your business?
• Can your people empathize to the benefits of organizing and classifying information and documents?
• Are they are likely obligated to enforce its classification?

Taxonomy project is a marathon like; simple but not easy. It will be impacted by the complexity of the organization process. It needs a good level of management support to influence participants and impose rules for efficient process application. Besides, expert matter workers involvement and availability is essential to make sure of the quality and correctness of the collected information which is critical to building an efficient enterprise taxonomy.  

I am done now, but I am going to write more posts to cover the subject from different corners, so please wait my next posts:

1. Deeper look into taxonomy types
2. Put into operation: Taxonomy implementation strategy.

Ibrahim Maro

My Blog,,,

I was reluctant to create personal blog, but not now. I am doing few researches, studies and preparing significant articles all about things I think I know about. ECM, Taxonomy, BPM and other related topics in the Information management of unstructured data.

Ohhh, I challenge myself in this and I am sure I can share & add something.

Please support me and wait my first blog about Taxonomy ;)