The Wecomplish Platform makes it easier to organize, reuse and improve insight, allowing us to spend more time focused on producing value and less time on interruptions and answering questions.
The Platform poses questions that ambitious teams need easily accessible answers to, enabling everyone to contribute to shared insight and a well aligned team.
In order to create an account for your organization, use one of the following account creation methods:
Use the quick start if you're looking to get a new installation and running as quickly as possible.
The quick start is available at https://app.wecomplish.no/quickstart
Use the wizard if you want more information to be pre-created as a part of the account setup
The wizard is available at https://app.wecomplish.no/hi
The setup wizard is available in English and Norwegian.
Here you will be asked a series of basic quesions about your organization in a chatbot-like manner. Once answered, a free 30 day trial account will instantly be created using your provided description of the organization.
If you do not opt to Upgrade to a paid account before the trial expires, access to your account will be revoked and you will be unable to log in.
To upgrade your trial account to a paid account, click the Upgrade-link in the yellow box in the top navigation, or go to Organization > Account > Subscription.
This brings you to the subscription management page detailing your existing subscription, and providing you with the option of upgrading to a paid account.
To upgrade to a paid account, click the "Switch to this plan..." button in relation to the plan you would like to upgrade to. Once your existing plan expires, you will be switched over to the new plan.
To change the email address of the invoice recipient, click the pencil-icon in relation to the "Billing details"-section.
Some pages within the platform include setup guides.
The intention of these guides is to help you get started by explaining the purpose of the page and the recommended steps to complete in order to gain the intended value from it.
If a page has a setup guide (and you have not already disabled it), the guide appears at the top of the page.
Here's an example of what a setup guide looks like:
The following pages have setup guides implemented:
To close (remove) a guide, click the "Close guide" button. Guides which have been closed can not be reopened.
Closing of guides is user-specific, meaning that if you close the guide on a page, the guide will still appear for other users (until they close it as well).
To get help, click the question icon in the top, right corner to trigger the context sensitive help menu, or use the keyboard shortcut h.
The help panel displays content from the documentation relevant to the page you're currently visiting.
When multiple documentation pages are relevant, click the title of the individual pages to expand and collapse their associated content.
Whenever you encounter unexpected behaviour from the Platform, we would love to hear about it so that we can fix it.
Please report the issue via email to your designated insight consultant.
Here's the information we require in order to understand the issue as quickly and with as little back and forth as possible.
Any screenshots (including the URL bar) explaining the issue is also greatly appreciated.
Whenever you feel that there's something missing from the platform, feel free to let us know.
We prefer feature request which focus on the problem the feature is intended to solve, rather than how you envision a solution.
A good way of requesting a feature is by means of a user story. A user story follows the following format:
As a [role] I would like to [action] in order to [benefit experienced].
A user story has the advantage of exposing:
Here are some examples:
Wecomplish helps you focus on the right stuff. Because when we work, it's easy to get caught up in the details and the familiar, and not see the bigger picture.
Many people have a tendency to spend too much time one zoom level deeper than their primary role suggests.
A team member may only be focused on their own tasks, whereas they should be focused on identifying and working more holistically on both their priorities and potential.
A team leader may be focused on his own work, whereas they should be more focused on supporting and enabling others.
An organizational leader may be focused on managing operational details, whereas they should be more focused on direction and organizational development.
This tendency may be caused by fact that when people are promoted or otherwise change roles, they are not neccessarily aware that their focus needs to change, nor do they understand what the new focus mode entails.
Here's a visualization of the different zoom levels, and the ideal primary focus based on role:
To create a better awareness of these zoom levels, Wecomplish uses the concept of focus modes.
This means that when you encounter the platform, you are be asked to select what you want to focus on, in the form of:
Use this focus mode when you have a contributor mindset, and want to complete the tasks assigned to you.
Use this focus mode when you have a team member mindset and want to identify your priorities and potential, and establish plans to work on them.
Use this focus mode when you have a team leader, mentor or facilitator mindset and want to enable others to move faster and do their best work.
Use this focus mode when you have the mindset of an organizational leader, architect, or would like to develop a birds eye perspective on the direction and status of the organization.
You. can toggle between the different focus modes in the upper, right corner of the current focus mode:
Perhaps you'll have one focus mode today, and another one tomorrow. Either way, focus modes help you and your team become more aware of and able to have a constructive conversation about how much time each individual should spend in each mode.
At any given time, there are expectations within a team that people
As a result, these expectations are either not adhered to very well, or might require a lot of time, repetition, friction and followup to get done right.
One way to reduce effort and friction as a leader is to identify these poorly operationalized expectations and make them the subject of clarification, training or perhaps even reconsideration.
Ideally, we would focus our efforts on those expectations that, if made more easily digestible, would have the biggest impact to the confidence, morale and productivity of the team.
What if you could identify those expectations, at the click of a button? The operationalization reports aim to do just that by providing you with a ranking of how poorly understood and automated individual expectations are.
This allows you to uncover new aspects of your business that you hadn't thought about, helps you spend your time more wisely, and focuses your efforts on where it will have the most impact.
The ranking of expectations is based on an impact score calculated based on the familiarity data collected by the platform.
The impact score takes the following parameters into account:
The worse something is automated, and the more people are expected to be familiar with it, the higher the impact score.
You can see the impact score appearing in different places throughout the different operationalization reports. Here is an example:
The operationlization reports are available at different zoom levels in the organization.
The organizational report takes the most zoomed out perspective by ranking how well expectations have been operationalized within each team.
The awareness, familiarity and impact indicators reflect the average of the expectations within the team.
Click a team card to zoom into the team operationalization report.
The team report exposes the individual the expectations within a team and ranks how well each individual expectation has been operationalized.
An expectation in this context is defined as a piece of insight which at least one role holder is expected to be familiar with.
The awareness and familiarity indicators reflect an average of the actuall awareness and familiarity as reported by the people expected to be familiar with it.
Here is what the top five items in a product team report might look like:
Clicking on a specific expectation gives you a detailed view of how familiarity is distributed across the different familiarity levels. Here you can more easily discover if the low ranking is a result of a lack of people indicating their familiarity, or if the indicated familiarity levels are low.
You can also request familiarity from the people who have not indicated it yet, by blicking the orange bell icon in relation to the "Unknown" familiarity label.
The person report exposes the featured expectations that a leader should focus on better operationalizing.
This report is accessible by navigating to the team focus of that individual, and selecting the Operationalization-tab.
The report displays all the teams that individual is responsible for, and the top 5 recommendations as identified by the impact score, or overridden recommendations.
There is only so much the system knows about your organization. As a result, you should not blindly accept the top ranking expectations as the ones to focus on.
Some expectations might take precendent due to circumstances or their expected impact on overall work.
You can combine system insight with your own personal insight by overriding recommendations. This is done by clicking either the "Pin recommendation" or "Reject recommendation" buttons, moving the recommendation to the top and bottom of the list respectively.
As the team and its amount of expectation grows, calculating the impact of each expectation can get time consuming.
To preserve the performance and user experience of the platform, report data is generated on demand, and cached for future page requests.
Generating, updating and removing the report data cache for a team is done on by manually by clicking the "Generate report"/"Refresh report" buttons on the organizational or team reports.
Recommendation overrides are lost when report data is cleared or regenerated. However, any user attempting to clear or regenerate report data will be made aware of and prompted to confirm deletion if any overrides exist.
The Wecomplish Platform makes it easier to share and improve insight into how teams operate, allowing us to spend more time focused on producing value and less time on interruptions and answering questions.
The Platform exposes questions that ambitious teams need great answers to, enabling everyone to contribute to reusable insight and alignment of the team.
To better understand how to achieve a high-performing team, read about how to build a great team playbook.
Answers are stored in Wecomplish as different types of information referred to as information types.
Wecomplish is focused on supporting the information types needed to produce a great team playbook.
Here are some examples of the information types supported and the questions they answer:
All the information types that Wecomplish supports, including the questions they are meant to answer, are viewable from the Overview.
You can access the overview by clicking the "Organization" link in the top, left navigation, and then selecting "Overview" in the left navigation.
By default, the overview lists all the information types that the Platform supports.
You can limit the list of information types to only contain information types you are expected to contribute to by selecting the "Only mine" view in the top:
Here's an excerpt of an overview in the context of an organization:
Each card represents an information type that can be managed within the Platform. The cards are devided into categories representing different insight management domains.
To indicate that you want to manage a specific information type within the Platform, click the "Start managing" button.
A card looks like this:
The card is blue if the information type is managed, and grey if it's not.
The card may contain the following information:
At which level of the information type management process the information type is. Only displayed if the information type is managed.
How many pieces of information are stored for this information type. Gives an indication of how important the information type is to the organization. Only displayed if any information exists.
The level of familiarity you have indicated for the information type. Hover over the indicator to see the date of indication and any additional notes. Click the indicator to be taken to the information type where the familiarity can be edited. Only displayed if familiarity has been indicated for the managed information type.
A warning is displayed if no roles have been selected as contributors.
The same is true if you are associated with a role which is expected to contribute, but you have not provided your familiarity yet.
Understanding and automating how information types relate to eachother is very useful for internalizing a mental model of how to describe the organization and making it more intuitive to navigate throughout the platform.
In order to understand how an information type relates to others, click the title of the information type you want to explore, or click the "Explore relations" button in the top, right corner to start exploration at the top of the hierarchy (the Organization).
When you are exploring the relations of an entity, the view holds the following pieces of relation information:
The relational view also displays some additional options related to the information type like its definition, a link to browse the information (if possible) and a link to the documentation.
Click the information type cards to continue exploring the network of information type relations.
Most software in use by organizations represent some type of information management system, in that they enable users to either create, process, store and/or transmit information.
When we think about and refer to systems in our work, we usually do it in terms of the information management domain the system designers have decided to focus on. We refer to systems focused on managing client information as CRM systems and systems focused on managing bookkeeping information as accounting systems.
Within these systems, the information types relevant for their respective domains are managed. Within CRM the information types might be prospects and deals, whereas in accounting it's vouchers and vendors.
If we look at this conceptually, we can see that both prospects and vouchers are just different information types, with potentially different organizational expectations associated with them. These expectations might include how the information should be formatted, where it should be maintained, by whom and how regularly.
In the context of the Wecomplish platform, information types are referred to in two contexts:
Firstly, the platform supports a large array of information types relevant to the team and organizational domain. We refer to these information types as insight types. For a detailed list of insight types supported, please review the the list of insight types.
Secondly, the platform has an "information type" insight type, enabling the team to communicate the expectations of individual information types across the various systems used by the team (not just the platform). Read more in the context of Systems.
Vi laget Wecomplish fordi vi savnet bedre oversikt over
Etter at vi tok i bruk Wecomplish jobber vi mer skalerbart og langsiktig, og får verdi ved at:
Wecomplish har et bibliotek hvor organisasjoner som bruker Wecomplish kan dele velorganiserte løsninger på felles utfordringer. Løsningene er enkle å kopiere inn i egen organisasjon for videre tilpasning og bruk.
Du finner følgende typer innhold i biblioteket:
For å gjøre en sjekkliste fra ditt eget team tilgjengelig i biblioteket, se Gjøre en sjekkliste tilgjengelig i biblioteket.
For å kopiere innhold inn til din egen organisasjon, trykk på kopieringsknappen øverst på innholdet.
Du vil bli bedt om å logge inn og deretter få muligheten til å velge hvilken organisasjon og hvilket team du ønsker å kopiere innholdet til.
At any given time, there are structures, expectations and insight within the organization that could benefit from some attention: Some are lacking, some are too complex, some are poorly understood, some are outdated, some are not performing as well as we would like and in some cases, we might realize that there really exists no proper insight at all.
Once you start realize this, a few things might start to happen:
To help you work methodically and organized with the improvement of insight, the platform allows you to flag insight you would like to designate attention, prioritize improvements in relation to eachother and delegate the responsibiltiy for improving different insights to different people.
Some use cases for flagging insight might be to:
When flagging, think of yourself as an organizational inspector, and the act of flagging as putting a red sticker on a part of the organization you would like to see improved or given special attention.
To flag a piece of insight, navigate to that insight and click the flag icon in the subheader.
When flagging, you will be asked to provide the motivation for flagging.
To unflag the same piece of insight, click the flag icon again.
The insight types which support flagging are listed in the flaggable trait.
To work with your flagged insight, navigate to Organization > Priorities > Flagged insight report, or clich the flag icon in the upper right corner.
From here you can:
The platform uses generative AI to assist you in your management of organizational expectations, including organizational leadership, learning and development.
Because generative AI processes can take some time to finish (expect 10 - 30 seconds), they are delegated to the background. This means that you can continue to browse and interact with the platform while the process finishes up.
Read more about background jobs.
Whenever a response is requested from the AI, it is first given the organizational context. This includes the
Please ensure that these pieces of information are up to date in order to help AI give you the best and most relevant responses.
Describing organizational expectations can be a tedious, laboursome and cognitively demanding process.
To help you lighten the load of coming up with and articulating expectations, the platform supports ideation.
Ideation is the process of generating ideas and suggestions. It is also commonly referred to as brainstorming.
The insight types which support ideation are listed in the ideatable trait. In addition to this list, ideation is also supported for
To trigger ideation, click the yellow "Have AI suggest..." button near the item list you would like to ideate. The button only appears when a list/field is empty.
Sometimes we can get a get a bit lost when it comes to making progress towards our priorities. When feeling stuck it's useful to have someone (or something) come up with helpful suggestions and challenge us to step out of our comfort zone.
To help you get unstuck the plattform imlements. the sparrable trait. Click the trait link to see which insight types are feedbackable.
When we have built something, critiquing it helps us gain a new perspective and make additional improvements.
To help you gain constructive feedback quickly, the platform implements the critiqueable trait. Click the trait link to see which insight types are critiquable.
To trigger a critique, click the three dots in the upper right corner, and select "AI critique".
Some actions within the platform can take some time to complete. Examples including adding large list of subtasks to a task, or requesting a response from the Generative AI.
In the cases where we suspect that the process will take some time to complete, the process is delegated to the background.
This means that rather than for you to have to sit around and wait for the process to finish, you can continue to navigate and interact with the platform while the process does its work.
When you trigger a time consuming process, a notice will appear in the top, right corner notifiying you that the process has been delegated to the background.
In addition, a yellow spinning cog will appear in the top navigation indicating that you have processes running in the background.
You can now continue to navigate around and interact with the platform while the process finishes. When it does, the cog will stop spinning and turn green.
To view the result of the background processes, click the cog icon to view the list of completed background processes. Click the individual item to be taken to the output produced by that process.
Sometimes background jobs fail. This happens most frequently with AI jobs, as the output of the generative AI can sometimes be unpredictable.
When a background job has failed, it will appear with the status of "Failed" in the background jobs list.
If a job fails once, we encourage you to try it again. If it fails multiple times, please get in touch with us so we can look into it.
On a desktop sized screen, the platform interface consists of three, main sections:
The top navigation consists of a left and right section.
The left section of the top navigation includes links to the main information types in the platform.
These are:
By click on the one of the information types, a dropdown opens where you can either go the complete list of items, search for an item within the given type, or select an item from the list of items you've recently viewed:
The right section includes links to commonly triggered actions:
The left navigation changes dependent on the selected navigation item in the top navigation.
That means that depending on the selected top navigation item, you may see one of four different left menus:
The left colum has a header signifying what type of navigation which is currently displayed, and a background color representing that type. The background color matches the selected item in the top navigation.
The text beneath the header displays the navigation context, meaning the name of the team in a team context, the name of a project in a project context, etc.
A lot of the time, the left colum is longer than the allocated screen height, meaning that you need to scroll in the left colum in order to reach the bottom most navigation items.
If you find the left navigation distracting, or just want a larger working space, you can minimize the navigation by clicking the double arrows near the top of the navigation column.
This will narrow the column down to just the icons representing the menu items. Click the double arrows again to expand the column.
When the column is minimized, you can hover over the icons in order to have the menu items appear.
The content area changes based on the selected navigation item in the left navigation.
The header represents the name of the current page. If they current page is hierarchically positioned under another page, you can see the parent page in smaller text next to it.
Existing information in the platform is editable via a dropdown menu in the upper, right corner. In order to trigger the menu, click the button with the ellipsis (...) icon in the upper, right corner.
The various edit actions available depend on the information type being edited. Provided that your user is granted access, you can always expect to find the ability to Edit and Delete existing information.
Some information types also support being moved, copied, etc.
To log in, go to https://app.wecomplish.no/ or directly to the tenant of your organization (https://[your-org].wecomplish.no/).
Log in using your email address and assigned password. Click the "Remember be" checkbox if you want to remained logged in across browser sessions.
If you are experiencing issues with logging in, it may be due to one of the following reasons:
Please make sure that you do not have any typos in your email address, and that the email address you are using is the one to which you received an invite from the system to log in.
Please make sure that there are no typos in your password.
If you are copying and pasting your password from your registration email, please ensure that you are not including any extra characters or spaces when copying.
If you have not received a password, or are unsure if you are using the correct password, you can use the "Forgot password" link on the log in page to set a new password.
Please make sure that you are logging in to the tenant of your organization. The URL in the browser should be https://[your-org].wecomplish.no/
To change the email address with which you logi in and receive notifications, go to https://app.wecomplish.no/my/profile
If you want, you may activate Tofaktorautentisering after logging in for improved security.
Wecomplish er en webbasert applikasjon. Det betyr at du som et utgangspunkt får tilgang til applikasjonen via nettleseren.
Ønsker du imidlertid raskere og enklere tilgang til Wecomplish finnes det forskjellige måter å tilgjengeliggjøre applikasjonen som et eget ikon/snarvei på enheten din.
Vipps – så har du laget snarvei til nettsiden (bakerst) på telefonen.
Det er fullt mulig å flytte på snarveiene: Hold fingeren på symbolet noen sekunder. Når den begynner å røre på seg, drar du den bare dit du vil ha den.
Stegene for å få Wecomplish som en egen desktop applikasjon er litt teknisk intrikate. Vi utfører derfor gjerne stegene for deg og sender deg en ferdig program-fil. Gi oss beskjed om du ønsker en desktop-app til Mac eller Windows.
Om du er teknisk kyndig kan du nyttegjøre følgende steg:
nativefier [org].wecomplish.no -i electron.icns -n Wecomplish --internal-urls ".*?\.wecomplish\.*?"...hvor [org] erstattes med subdomenet for din Wecomplish-installasjon.
The user interface in Wecomplish is available in Norwegian and English.
In order to change the default language of the organization, go to Organization > Settings > Default language.
To override the language selection for an individual user, edit the users preferences.
A common practice when collaborating is to check in with each other on a regular basis in order to see how work is progressing and if assistance is required.
The platform allows for the logging of such check-ins through a streamlined check-in process which reuses the existing focus data of individual users.
The purpose of the check-in functionality is to ensure that check-ins happen, and that they are as effective, efficient, accountable and on-point as possible.
By utilizing check-ins we
In order to log a check-in with someone, go to the Focus-dashboard of that person and click the "New check-in button.
This will first take you to the check-in preview.
The purpose of this step is to:
The left column contains the different steps that can be checked in with. Hover over each item to see an explanation.
Toggle the checkbox to include or exclude the step in the check-in. By default, steps which have data are pre-selected to be included. If the step has been checked in previously, you can see how long ago since someone checked in with this person and the particular step.
The different types of check-inable items are:
Each step lists the items the person you are checking in with is currently focused on, and an ability to add notes in association to those items where relevant. The right column displays an indicator or which check-in step you are currently on, and a list of generic discussion questions related to the the current step.
For each item in the check-in process, you can add relevant notes. These might be feedback, additional info or things to followup on in upcoming checki-ins.
To add a note, click the grey "Add a note" label.
If an item has a note from a previous checkin, a purple label is displayed indicating the last time a note was added to this item. Click the label to expand the actual note.
If you reach a step which does not correctly reflect the current priorities of a person, use a separate tab to remove outdated prioritites and/or add missing prioritites, and then click the "Refresh" button in the lower, right corner.
This will fetch an updated set of priorities, while maintaining any comments you have added to pre-existing prioritites before refreshing.
In order to review a past check-in, go to Support Others > Check-ins of the person who did the check-in, and select the relevant check-in from the list. Individual check-ins are only viewable by the person who did the checking in and the person who was checked in with.
The check-in view includes a list of the items checked in with and their associated notes in the left column, and a navigation in the right column indicating the various item types, their count and whether or not there are notes associated with those item types.
To ensure that people are actually being checked in with, use the Individual priorities report, accessible from Organization > Priorities > Individual priorities.
The Individual priorities report exposes when a person was last checked in with, and the percentage of people who were checked in with during the last 7 days.
To search, click the search icon in the top, right corner or use the keyboard shortcut s.
The following information types are searchable:
You can use the arrow keys to change between the selected item in the search results and the "Enter" key to go to the selected item.
The information available in the search depends the access level of the logged in user.
If you're not sure what you're looking for or don't know the name of it, you can use the Browse view as an alternative to search when locating information.
The browse view displays all information stored across all the teams you have access to in one, convenient location. To access the Browse view, select Organization and then Browse in the left hand navigation, trigger the search panel (keyboard shortcut "s") and click the "Browse" link.
To browse, select the information type you want to explore. This will list all the information for that information type. Use the right column to filter the list by searching for a piece of text contained within the information type.
Some information types support additional categorizable filters like team, categories, etc.
Bookmark are a way of easily and quickly getting back to information you access often.
Add/remove a bookmark to a page by clicking the star icon to the right of the page title.
To view your current bookmarks, click the star icon in the upper, right corner or use the keyboard shortcut b.
See the bookmarkable trait to uncover which insight types support bookmarking.
There are two options when you want to to add new information to the platform:
Information in the platform is mainly created via green buttons displayed in relation to information lists where the information it expected to be stored.
These buttons can generally be found in the upper right corner of list pages
...or to the right of headings representing a section where additional items can be added.
Quick creation allows you to create new content regardless of where in the platform you are currently located.
In order to quick create information, click the "Add information" button in the top, right corner and select the type of information you want to create. Scroll within the panel to see all the options.
Alternatively, use the keyboard shortcuts as displayed when hovering over an information type.
The following information types are supported by quick create (keyboard shortcuts in parentheses):
Allthough unique insight can be what sets an organization apart, a lot of insight is reusable across organizations and does not make sense to reinvent.
To save you time and reuse the mental efforts of others, we offer the Wecomplish library. The library contains generalized insight that can be easily copied into your own organization where you can reuse and adapt it to your particular needs.
Insight from the library is made accessible in the following ways:
For users who do not yet have their own Wecomplish-account, the library is searchable and browseable when click the Library menu item on the public facing website.
When you are adding new content (like adding a role), there are some places which support selecting content from the library.
You can tell that an information type supports library-selection if the "Browse library" button appears.
When you select content from the library, that piece of content will be copied into the team.
The following information types support library selection when adding content:
When you are looking to link up content to eachother (like linking which roles are assigned to a person), there are some places which support selecting content from the library.
You can tell that field support library-selection by clicking the "Browse all" button and look for the "Wecomplish library".
When you select content from the library, that piece of content will be copied into your organization. If you have more than one team, you will be promped to select into which team the content should be stored.
The following contexts support library selection:
Content that is marked as publicly available is automatically made available in a preview mode. The preview mode of a piece of information is available to anyone on the internet, regardless of whether they are logged in or not.
The purpose of the preview mode is to allow users to preview a particular piece of information in order to consider copying it to their own organization, or simply to use it as inspiration.
When adding content and browsing for linked content, click the purple eye icon to preview the content.
For information publically available within your own organization, you can view the preview mode of a entity by clicking the yellow padlock icon indicating that the content is publicly available.
Advanced use
If you want to highlight a particular piece of information when sharing a preview with someone, you can use the following parameters to expand items and scroll to them respectively:
Point to the item or category in order to determine it's ID.
Here's an example of an URL which opens item 33 and 34, and scrolls to item 33:
https://app.wecomplish.no/preview/skillset/680/insight-management-basics?open[]=33&open[]=34#item-33
Any organization using Wecomplish can make content available in the library. To make the content available, edit the piece of information and check the "Publicly available" checkbox.
The following information types support being made available in the library:
If you want to limit the content you're seeing when browsing to the content provided by the Wecomplish organization, use the Organization-filter.
The front page of the library includes a "Featured content" section, which showcases some of the content that can be found in the library.
The purpose of the featured content section is to create interest and better get a feel for what sort of content one can expect to find in the library.
The content is horizontally scrollable, meaning that one can either click the left and right navigation arrows, or use the swipe action on your device to scroll between the featured items.
The featured content section is divided into a Work and a Life section, where the Work section is the one visible by default.
The specific content displayed in the featured content section is managed in the platform code base.
Most of the content in the library can be bookmarked. The motivation for bookmarking pieces of information is to collect information that is relevant to you or someone else, in order to review it all in one place, or share it with others.
The following information types support bookmarking:
To bookmark a piece of information, click the small, purple button with the bookmark icon in the line or full view of the piece of information.
This will produce a dropdown menu where you can choose to bookmark the item, or add it to a specific bookmark collection.
To view all bookmarked pieces of content, click the bookmark indicator in the top, right corner.
Bookmark collections allows you to group a set of bookmarks with a specific purpose. Use cases might be wanting to share a specific collection of resources with a friend or colleague, or creating a more generic, bookmark collection that you think might be suitable for types of people you encounter more often.
Bookmark collections work similar to how you playlists work in an app like Spotify.
To add a bookmark to a bookmark collection, click the bookmark indicator and select the collection in question, or create a new collection.
To view all existing bookmark collections, click the bookmark indicator in the upper, right corner.
To share a specific bookmark collection with someone else, click the "Share" button in relation to the collection.
To edit or delete a bookmark collection, click the name of the collection and then the Edit or Delete button.
Assessments are meant to help you systematically organize input on potential from both yourself and others, and use that information to prioritize your development efforts.
An assessment is a high-level, opinionated perception of how well someone masters a role or a skillset, and how impactful we would expect it to be if they were given the proper development opportunities and applied themselves.
Read more about the concept of assessments.
In the context of the library, assessments are meant to help you build awareness and identify where it potentially makes sense to dive deeper in and Test yourself.
To make an assessment, navigate to the item in the library in which you want to assess ability, and trigger a new assessment by clicking the green star indicator.
You can trigger an assessment in the following contexts:
Once you have been taken through each assessment item, you will be sent to the assessments page which lists all your assessments, grouped by information type, and sorted in descending order of your potential.
Once you have assessed yourself in something, a indicator is shown communicating your potential.
The potential indicator has four levels:
To view all your assessments in one, convenient location, click the Assessments indicator in the top, right corner.
When you trigger a new assessment, the default assumption is that you want to assess yourself. However, you can just as easily add other people and assess them. Typical use cases for this is coworkers or partners invested in helping each other improve.
To add a new person to assess, trigger a new assessment and click the "Add new person" link, or click the assessments indicator in the top, right corner and manage the people you want to assess from there.
Using the library, anyone can test themselves to see how familiar they are with a role or skillset. Testing yourself does not require any form of registration.
The purpose of this feature is to:
To test yourself, navigate to a role or skillset in the library and click the "Test yourself" button.
This will cycle you through the particular expectations of the selected role or skillset allowing you to reflect on your familiarity and what's holding you back.
Once you're done, you are sent to a summary page showing your overall familiarity, and your familiarity with the individual expectations.
Being able to expose, explore and understand how different pieces of information relate to one another is one of the significant advantages of the platform.
Much like the hyperlinks of the internet allows you to explore different topics, the platform uses the concept of related content to tie together different pieces of information that are relevant to eachother.
Some typical use cases for related content include:
Here's what some different pieces of related content look like in the context of a responsibility:
To add a piece of content as related, click the green plus icon in relation to the "Related content" header on the relevant page, and search for the content you would like to add.
For a complete list of insight types which support being added as related content, check out the Relatable trait.
If you are tagged (using the @ sign) in a comment you will, in addition to receiving a notification (applies only to tasks) also receive an item in your inbox. The purpose of the inbox is to ensure that comments requesting your specific attention don't get lost.
If there are any unread items in your inbox, they will be displayed in the right column of your focus dashboard, beneath the personal development section, sorted from the youngest to the oldest item.
Items in the inbox are automatically marked as read when you reply rr react to the comment in which you were tagged. You can also manually mark inbox elements as read manually by clicking the checkbox icon in association to the relevant inbox item.
For some activities within the platform, email notifications are sent out.
How quickly a notification is sent from the system depends on how "nice to have" the notification is assumed to be.
If you are tagged in a comment on a task or an observation, you will receive a notification within the next 5 minutes.
For tasks you follow or observations you holde a role in, the default platform behaviour is to send you a daily summary of activity.
For tasks, check out Følgere for which types of activities followers are notificed of.
For observations, anyone holding a role in the observation are notified of new comments.
If you want to be notified within a 5 minute period for these types of notifications as well, you can activate this in your personal settings.
If you or someone else is particularly interested in a piece of information or the activity surrounding it, you can add that person as a follower.
A follower will get Email notifications when key activities are triggered.
The following information types support following:
| Information types | Followers are notified of |
| Task |
|
| Wiki (page/section) |
|
| Survey |
|
| KPI group |
|
| Health checks |
|
For å lenke mellom innhold i Wecomplish, bruk formatet !X123 hvor X representerer forbokstaven til typen innhold det lenkes til, og 123 representerer ID-en. Finn ID-nummeret som de siste sifferne av URL´en.
Skriv eksempelvis ! (utropstegn) etterfulgt av:
Følgende entiteter støtter å bli internlenket til:
Fordelen med å bruke internlenker fremfor harde lenker er at lenken vil gjenspeile oppdaterte navn på entiteten det lenkes til og at navnet vil være gjennomstreket dersom entiteten er lukket.
Dersom du kun ønsker å få produsert lenken til innhold i Wecomplish, men selv styre hva lenken heter kan du bruke | fremfor !, eksempelvis:
Kommentarer og beskrivelser støtter Github flavoured Markdown.
Les introduksjon til kommandoer.
Om Markdown er nytt for deg er det spesielt nyttig å lære seg:
Du kan reagere ved hjelp av emojis på forskjellige typer innhold i Wecomplish og se hvem som har reagert på ditt innhold.
Det er mulig å reagere på følgende innhold:
For å legge til en reaksjon, trykk på smilefjeset i tilknytning til innholdet du ønsker å reagere på.
Dersom det ikke har vært reagert på innholdet tidligere vises smilefjeset øverst til høyre:
Dersom noen allerede har reagert kan du legge til ytterligere reaksjoner ved å trykke på smilefjeset ved siden av de eksisterende reaksjonene, eller ved å trykke på en av de eksisterende reaksjonene.
For å fjerne en av dine reaksjoner, trykk på reaksjonen du ønsker å fjerne.
Pek på reaksjonen for å se hvem som har reagert.
For å se alle reaksjonene på ditt innhold, klikk på menyvalget Meg > Reaksjoner i venstre kolonne.
Menyvalget viser en grå indikator når du har nye (uleste) reaksjoner.
Innhold i Wecomplish er ordnet i et hierarki. Hvilken del av hierarkiet innholdet tilhører styrer hvem som har tilgang til innholdet.
Administratorer har tilgang til alt innhold. Team-medlemmer kan kun se innhold tilhørende sitt eget team.
Innholdets nåværende plassering gjenspeiles i brødsmulestien.
For å flytte innhold, trykk velg "Flytt" fra nedtrekksmenyen øverst til høyre , eller bruk tastatursnarveien Shift + Cmd + P (for Parent).
Søk opp innholdet du ønsker å legge inneværende innhold under, og velg denne.
Følgende typer innhold kan flyttes på denne måten:
Kan plasseres underlagt:
Dersom du forsøker å søke opp en konkret oppgave, men ikke får opp oppgaven opp blant topp-treffene kan du søke opp oppgaven ved hjelp av oppgavens ID i stedet.
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plaseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Kan plasseres underlagt:
Prompter plasseres underlagt:
Using the verification functionality you can verify that the information on a given page is accurate and up-to date, or request that someone else verifies the information.
Relevant use cases are:
Pages where the information can be verified are identified by the shield icon to the right of the page title:
Hovering over the shield will indicate the verification status of the page. There are three indications:
Indicates that the information on the page has never been verified.
Indicates that the page is pending at least one verification request.
Indicates that the page has been verified.
Click the verification indicator or use the keyboard shortcut "v" to toggle the verification panel for the page you're looking at.
When the page has no prior verifications, the panel looks like this:
If you hold the best source of truth for whether or not the information is accurate and up-to-date, you can quicky indicate this by clicking the "Verify that the information is accurate" button. This will move the verification indication to the verified state.
If you suspect that other people might be better equipped at verifying the information, you can easily request their assistance.
Click the "Request information from someone else" button and fill out the form that appears.
When you click the "Ask for help" button an email is sent to the person you selected notifying them of your request for help. The email contains a link that will take them to the page with the verification panel open, which will appear something like this:
When the invitee has reviewed the information they can change the state of the verification from Uncertain to Verified. This will send an email to the person who requested the verification notifying them that the information has been verified, and the verification panel will look like this:
If you want, you can request verifications from multiple people.
A good use case for this might be to ensure ownership to the information across a group, or when there are multiple people each holding a section of the entire picture.
For power users, there are multiple keyboard shortcuts scattered throughout the platform to make navigating the platform more efficient.
The most common, global keyboard shortcuts are collected here for convenience:
In order to prevent duplication of information, the Platform produces a warning whenever you create a new item for which there aleady exists an item with the same name.
The warning appears in the top, right corner of the next page load, including a link to the duplicated item.
For a complete list of insight types which are checked for duplication upon creation, check out the Duplication preventable trait.
The default behaviour of the platform is to make information easily accessible and editable. This is based on a belief that the more people are able to contribute to the information, the greater the probability is of the information improving in quality over time.
However, some information is not meant to change a lot, and some might even be harmful and non-compliant if it were inadvertantly changed.
To accomodate this use case, the platform implements the concept of locking down information. Locking a piece of information limits edit access to only admins.
The ability to lock piece of information appears near the bottom of a page. The option only appears if you are an admin. You also need to be an admin in order to actually lock and unclock information.
If a piece of information is locked, this will appear to everyone.
The following information types support locking:
The Platform has a lot of features. However, any given moment in time, only a subset of the available features might be relevant to a specific individual, team or organization.
To make it clearer which features are expected to be used you can disable the features you don't need, care about or are. handling in some other way.
The following supports being disabled:
To disable a feature, first navigate to the context in which you want to disable the feature.
Then, select the "Disable" option from the dropdown menu in the upper, right corner.
From this view you can disable specific items (i.e. perspectives or insight types) that the person, team or organization is not expected to use at the present moment.
The organizational overview provides transparency into how an organization operates by starting with a birds-eye overview of the organization.
From here you can use the platform to explore and explain the organization via different organizational perspectives in order to better understand, improve and contribute to it.
The overview consists of three primary sections:
This section describes the direction of the organization. It is broken down into the organization's
If these directional concepts are unfamiliar to you, you can read more about them and how they differ in the Organizational identity skillset.
Core values, when done right, guide everything you do at work.
If you are unfamiliar with the concept of values, you can read more about it in the Values-documentation.
Organizational perspectives are the different ways in which we can examine the organization. Which perspective makes sense to use at any given time depends on what you're trying to uncover or explain.
People responsible for ensuring a healthy and resilient organization should take care to regulary cycle through the different perspectives in order to ensure that they are properly adhered to.
Read more about Organizational perspectives.
Organizational perspectives are the different ways in which we can examine the organization. Which perspective makes sense to use at any given time depends on what you're trying to uncover or explain.
People responsible for ensuring a healthy and resilient organization should take care to regulary cycle through the different perspectives in order to ensure that they are properly adhered to.
Here are the different perspectives supported by the platform, and when it might make sense to use them:
The teams perspective presents the organization as a set of teams working together towards a common purpose.
Use the teams perspective when you want to understand or communicate how the organization has organized its work, and who is contributing to which types of work.
The people perspective presents the organization as a set of people contributing to the organization.
Use the people perspective when you want to understand or communicate the size of the organization, who reports to who, and the priorities, plans and development of each individual.
The insight perspective presents the organization in terms of it's know-how.
Use the insight perspective to understand and communicate what the organization has learned about itself and the market, and how it informs its day-to-day work.
The development perspective presents the organization in terms of it's health and how we are working to improve our teams and our people.
Use the development perspective to understand and communicate the current organizational health indicators, to which extent development efforts are happening, how far along each team and individual has come, and where support is needed.
The leadership perspective presents the organization in terms of it's leadership.
Use the leadership perspective to understand and communicate to which extent people are being supported and held accountable to their priorities and potential.
The priorities perspective presents the organization in terms of what it is currently focused on.
Use the priorities perspecticve to understand and communicate what is currently considered most important.
The activity perspective presents the organization in terms of what people are doing.
Use the activity perspective to understand and communicate who is contributing to the insight contained within the platform, and how they are contributing.
Organisational values, when done right, guide everything you do at work.
They describe the core ethics or principles which the company will abide by, no matter what. They inspire employees’ best efforts and also constrain their actions.
Strong, clearly-articulated values should be a true reflection of your organisation’s aspirations for appropriate workplace behaviour, and play an important role in building a positive culture in your organisation.
Well-drafted and current organisational values:
Every organisation preferences some values over others. If you are unfamiliar with values as a concept, check out this article for a list of value examples, and this article which discusses the dangers of half-assing a values initiative.
To manage the values of your organization, click Organization in the top navigation and look for core values in the right column.
Values support familiarity and related content.
Go to Organization > Teams and click the green plus icon. Alternatively, use quick create.
Provide the team name and the optional parent team.
A team can have one of two access levels, open or private. Read more about how to change the team access level in Users and access.
Open teams are available to any user in the organization. Private teams are only available to those with specific access to the team.
To grant a user access to a private team, navigate to the team and select "Access" in the left colum menu.
From there you can add either a new user to the team, or an existing user aleady registered with the organization.
If you would like to add a user which you know already has a Wecomplish account within a different organization, use the "Add new user" option, but only fill out the email address field. The remaining fields will automatically be fetched from the existing user account when added.
Team members are the people who are expected to contribute to a team.
Assigning team members is done by assigning someone a role in the context of that team.
The people who have a role in the team are displayed in the upper right corner of the team card, and as a list on the team dashboard.
Indicate the position of a person in the organizational hierarchy (meaning who they report to and who reports to them) by adding their leaders and or/direct reports in the right column of their profile page.
The list of people in the organization (Organization > People) is indented in accordance with the organizational hierarchy to produce a simple Organizational chart.
Leaders receive Notification of completed familiarity.
Brukeren vil motta en e-post med brukernavn og passord til innlogging. Brukere med tilknytning til ett team vil automatisk videresendes til sitt teams oppgaveliste når de logger inn.
Notes are a simple when of jotting down and collaborating around a thought, an idea or the minutes of a converstation.
You have access to view and edit the notes you have created yourself, and the ones to which you have been assigned the role of contributor.
In order to view your notes, select Improvement > Notes in the left colum navigation.
The notes are sorted from youngest to oldest by last edit date.
If the note has no title, and excerpt from the body is displayed as the summary of the note.
You can create a new note in one of two ways:
The changes you make to a note are automatically saved when you stop typing. If anyone else has edited the same note in the meanwhile, you will be notified.
You can collaborate on a note by adding contributors. Users added as contributors can view and edit the note.
Viser KPI gruppene du har rollen som bestiller, ansvarlig eller produsent, gruppert på hyppigheten de forventes produsert (hyppigst først).
Mine aktiviteter lar deg bedre og enklere forsikre at tid ført matcher det du har gjort.
Les mer om aktiviteter på What are activites.
Brukergrensesnittet viser som standard informasjon for dagens dato. Ved å legge til /YYYY-MM-DD(eks. /2018-01-01) til URL-en kan du se din tid og aktiviteter for en annen dato.
Tid ført vises på en tidslinje som gjengir den aktive datoen.
Tidslinjen strekker seg fra den aktive datoens tidligste til seneste aktivitet eller timeføring. Pek på tidslinjens ytterpunkter for å se hvilken tidsperiode tidslinjen strekker seg over.
Aktivitetene vises i grupper basert på tilknytning. Aktivitetene kan være knyttet til et av følgende grupperingsnivåer:
Grupperingsnivåene er gjengitt hierarkisk, slik at oppgaver viser under relevant prosjekt, og prosjekter under relevant team.
Innenfor hver aktivitetsgruppe er aktivitetene gjengitt på en aktivitetsindikator. Indikatoren er inndelt i perioder med samme målestokk som tidslinjen.
Aktiviteter gjenspeiles med ett mørkegrått felt i høyden pr aktivitet.
Aktiviteter hvis relasjon til team ikke kan identifiseres (eksempelvis fordi det er kommentert på en oppgave eller observasjon som senere er slettet) vil samles i en gruppe med navn [Ukjent].
Ved pek på tidslinjen fremheves tilsvarende periode (og evt aktiviteter i perioden) på aktivitetsindikatorene. Dersom du peker på et felt med tid ført fremheves også aktivitetsgruppen timeføringen er knyttet til. Dette kan brukes til å kontrollere at timeføringen matcher aktivitetsnivå.
Ved pek på en aktivitetsindikator fremheves samme periode på øvrige aktivitetsindikatorer, samt på tidslinjen.
Du kan velge en eller flere deler av tidslinjen ved å klikke på disse.
Trykk på "Opphev valg" for å deaktivere valg av samtlige perioder. Lenken vises kun dersom minst en periode er valgt.
Når du har valgt en eller flere perioder vises kun aktivitetsgrupper med aktivitet innenfor de valgte periodene. Dersom ingen aktivitetsgrupper har aktivitet innenfor de valgte periodene vises alle aktivitetsgrupper.
Dersom du har valgt en eller flere perioder med tid ført vises timeføringene for disse periodene. Du kan peke på en periode på tidslinjen for å fremheve den enkelte timeføringen for denne perioden.
Dersom du har valgt en eller flere perioder uten tid ført utløses timeføringsskjemaet ferdigt utfylt med start- og slutttid tilsvarende første og siste periode uten tid ført for den valgte perioden.
Dersom du i tillegg klikker på en av aktivitetsgruppene fylles også automatisk timebeskrivelsen ut med en beskrivelse av aktivitetene for den valgte gruppen. Dersom aktivitetsgruppen er for en oppgave fylles også automatisk feltet for relasjon ut.
To edit the personal settings of a user, navigate to the user in question and select the "Edit profile" option from the action dropdown.
Lar deg spesifisere for hvilke perioder en bruker har kapasitet, og evt mengden belastbar kapasitet for perioden.
Det er ikke nødvendig å spesifisere redusert kapasitet for helligdager, da disse trekkes ut i rapporter automatisk.
Valg av første leveransedato er obligatorisk. Dersom ingen siste leveransedato settes regnes kapasiteten for å vare i det uendelige.
Ved overlappende kapasitetsperioder vinner perioden med siste leveransedato over perioder uten siste leveransedato, og perioder med kortere varighet over perioder med lengre varighet.
Du kan gjøre det vanskeligere for uvedkommende å få tilgang til dine data i Wecomplish ved å aktivere tofaktorautentisering.
Tofaktorautentisering betyr at du i tillegg til passord må angi en engangskode hver gang du logger inn.
Engangskoden får du fra appen Google Authenticator etter at du har lastet ned denne fra din telefons app store og skannet QR koden for tofaktorautentisering i Wecomplish.
For å sette opp tofaktorautentisering, gå til Meg > Innstillinger > Preferanser > Aktiver tofaktorautentisering og følg instruksene på skjermen. Når tofaktorautentisering er aktivert kan du deaktivere autentiseringen fra samme side.
Dersom du vil kan du aktivere funksjonen for ukentlig statusrapport. Dette gjør du ved å gå til Meg > Innstillinger > Preferanser og kryss av for å motta ukentlig statusoppdatering pr e-post.
Når funksjonen er aktivert vil du få en e-post hver mandag morgen med informasjon om:
Dersom du ikke har hatt noen aktivitet foregående uke, ingenting avventer deg og ingenting er planlagt, vil du ikke motta noen e-post den uken.
Du kan også gå til /review/week for å se innholdet i e-posten slik den ville blitt sendt deg for inneværende uke.
Tid du har ført. For mer informasjon, se generell dokumentasjonen for timerapporter.
Mine oppgaver viser en liste over oppgaver som du har ansvaret for og en liste over oppgaver som du har bestilt. Sistnevnte vises kun dersom antallet oppgaver er under 500 stk.
Flere forskjellige steder i Wecomplish er det mulig å legge til en kommentar. Noen steder produserer kommentarene også Email notifications.
Det er mulig å legge til kommentarer på følgende innholdstyper:
For å redigere en kommentar, trykk på pilen som peker nedover i kommentarens øvre høyre hjørne og velg "Rediger" eller "Slett". Vanlige brukere kan redigere egne kommentarer. Ansattbrukere kan redigere alle kommentarer.
Kommentarer støtter rik formatering. Etterhvert som du skriver en kommentar vises en forhåndsvisning av hvordan kommentaren vil bli seende ut under.
Dersom du er en ansatt og ønsker at en kommentar ikke skal være synlig for kunder, krysse av for "Skjult for kunde" i sjekkboksen, eller ved hjelp av tastatursnarveien Cmd + K.
En skjult kommentar gjengis med grålagt bakgrunn for andre ansatte og er ikke synlig for vanlige brukere.
Trykk på "Ny kommentar" og skriv inn din kommentar. For å lagre, trykk på "Lagre" knappen eller bruk tastatursnarveien Cmd + Enter.
Dersom du ønsker å be om tilbakemelding eller trekke en persons oppmerksomhet spesielt mot en kommentar kan du gjøre dette ved å skrive @ etterfulgt av navnet eller e-postadressen til vedkommende. Når du skriver @ vil det komme opp en liste over forslag bestående av alle dine team-medlemmer.
Brukere som @-es vil få et element i innboksen sin og potensielt et Email notifications avhengig av om dette er støttet for typen innhold.
Check out Create an account.
Lar deg legge til og fjerne administratorer av organisasjonen. Se Users and access for mer informasjon om administratorers rettigheter.
Fra denne siden kan du eksportere alle data som din organisasjon har lagret i Wecomplish, eller gjøre dataene tilgjengelige for en Wecomplish utvikler for å gjøre feilsøkingen av et problem mer effektiv.
Du må ha rollen admin for å få tilgang til å se og opprette data eksporter. Du har rollen admin dersom du opprettet organisasjonen.
Data eksporten produseres som SQL insert statements. Dette gjør eksporten velegnet til:
Følgende e-postvarsler produseres i tilknytning til dataeksporter:
Legg inn ferie på tvers av hele organisasjonen.
Ferie overstyrer (nullstiller) Kapasitet for samtlige team-medlemmer for perioden, og viser et varsel i toppen av alle sider om at organisasjonen er på ferie i perioden hvor ferien er angitt.
Legg til, endre slette og ordne observasjonskategorier.
Observasjonskategorier brukes til å klassifisere observasjoner etter type og deres relative prioritet. Når observasjoner vises i en liste vises de gruppert på observasjonskategori og sortert synkende etter observasjonskategoriens prioritet.
Observasjonskategorier markert som "Haster" vil resultere i at observasjoner som bruker denne kategorien vil få spesiell oppmerksomhet i listen over den enkeltes observasjoner.
For å endre på observasjonakategorienes prioritet, dra og slipp kategoriene i ønsket rekkefølge.
Her er et eksempel på observasjonskategorier som du kan vurdere å bruke som utgangspunkt for din egen organisasjon:
Legg til, endre og slette lønnsarter.
Lønnsarter brukes (valgfritt) når man registrerer timer for å klassifisere hva slags type lønn som forventes for arbeidet.
Timerapportene gjør det mulig å gruppere timer pr lønnsart.
Tilpass organisasjonens innstillinger.
Her kan du endre navnet på organisasjonen slik dette refereres til på forskjellige steder i systemet.
Her kan du inn egen CSS kode for å tilpasse applikasjonens utseende til organisasjonen.
Å legge inn egen CSS-kode kan være spesielt nyttig for brukere som er medlem av flere organisasjoner, da en visuell distingvering vil gjøre det enklere å skille mellom når man befinner seg i hvilken organisasjon.
En enkel CSS-tilpasning kan gjøres ved å inkludere følgende kode, hvor #HEX erstattes med organisasjonens primærfarge.
.button, .button:hover, ul.menu li a:hover {
background-color: #HEX;
}
ul.menu li a {
color: #HEX;
}
Her kan du legge nettadressen til et skreddersydd favicon slik at det er enklere å identifisere din Wecomplish installasjon i listen over faner.
Her kan du styre hvilken e-postadresse som skal motta fakturaen for organisasjonens Wecomplish abonnement.
Using the Profile view of a person you can gain instant insight into how that person is contributing and working. This makes it easier to ensure that everyone have what they need in order to produce meaningful outcomes for the organization.
To see the profile view, select the indivial person from Organization > People, or search for the name of the person for which you would like to see the profile.
Here's an excerpt of the profile view for a single person:
Use the insight on the profile to determine if the person:
In the platform, programs represent a collection of resources we would like people to step through in order to better prepare for existing and future roles.
Some use cases for programs include:
When creating a program, you can decide between building one from scratch, or copying a program from the Wecomplish library. To do the latter, click the
Selecting a program from the library will copy the program and all it's publicly available resources.
Click the purple eye-icon to preview the contents of a program before copying it.
Once you have created or copied a program, you may select which resources to add. See the programmable trait for which types of resources support being included in a program.
Use the sort-handle to drag and drop resources in the order you prefer participants to go through them.
In order for someone to be exposed to a program, you need to add them as a participant. A participant can be any pre-existing user within the platform.
To add a participant, select the participants tab, clich the "Add participant" button, and start typing to search for the user, or click the "Browse all" to search for users.
To view participant progress, click the name of the participant in the participant list, or navigate to the dashboard of that user and locate the "Potential" section of the Me-focus.
From the dashboard, you can see the amount of resources completed, how long ago since the last time there was any program activity by the participant, and any expectations that the participant may find unclear or would like some assistance with.
By clicking into the program you get a more detailed view of the progress and evaluation of each resources. Here, the resources not yet completed are grouped at the top, and the completed resources are shown at the bottom, sorted in descending order by participant evaluation.
The evaluation is based on the participant familiarity with the resource, expect for surveys and healthchecks where the evaluation represents the survey response and check-in score respectively.
The Program overview shows all the programs within the organization, grouped by team and category, and displaying the participants of each program.
Navigate to the program overview by selecting Organization in the top navigation, and then Enablement > Programs in the left column.
After some time has gone since your familiarity indication, you might want to refamiliarize yourself again. Use cases for this include:
You can refamiliarize yourself with roles and skillset. The button for refamiliarization appears on the role or skillset assignment page, if there is more than 30 days since you last updated your familiarity with one of the expectations.
One you click the "Update your familiarity" button, you will be brought through all and any expectations where the last time you updated familiarity is more than 30 days ago.
Ensuring that people grow and remain familiar with policies, responsibilities, skills, etc is one of the great operational challenges of an organization. And the more often there are changes in people, roles or expectations, the more challenging it becomes to keep expectations and familiarity in sync.
To address this challenge we allow for people to communicate to which extent they are familiar with something. We refer referred to as familiarity.
Familiarity provides us with a more effective and efficient way of identifying and updating people's understanding of, belief in and comfort with something.
We find familiarity to be a great indicator of to which extent a person can realistically be expected to to comply with expectations, and a useful way of communicating the levels involved in reaching an operational and value-adding state.
When someone indicates their familiarity with something, they are prompted to select from one of four levels. These are:
Here's an example of familiarity indication in the context of a system:
The familiarity levels builds on top of one another. That means that if you indicate that you are Comfortable, you are also expected to Understand, and if you indicate that you are Automated, you are also expected to be Comfortable.
As a leader (or any person having expectations of someone else, for that matter), consider the fact that we can't realistically expect people to predictably meet an expectation unless they have indicated that they are Automated.
When familiarity data is aggregated and reported on, it is reported as two percentages:
The percentage is calculated relative to the context.
You'll usually see these indicators appear next to eachother, in the form of two progress bars:
The awareness percentage indicates if any familiarity has been given (regardless of level), whereas the familiarity percentage takes the explicit familiarity level into account.
The point of distinguishing between the two is that we want to focus on building awareness of expectations first, and then later focus on improving familiarity levels where neccessary.
Read more about how to explore familiarity.
The overview of the familiarity information type describes which specific information types that support indicating familiarity (in the "Outgoing associations" column).
You can also identify if a specific page supports familiarity by whether or not the familiarity icon appears on the right hand side of the subheader.
When you have indicated your familiarity with something, the icon is replaced a familiarity indicator indicating your current level of familiarity:
People sometimes confuse the platform concept of familiarity with the platform concept of proficiency (the latter being related to skillsets).
It makes sense to distinguish the two concepts like this:
Communication of familiarity is done via the familiarity panel. From this panel you can:
When !ddocs, the panel is automatically opened. To open and close the panel manually, click the familiarity indicator icon in the top, right corner or use the keyboard shortcut f.
The familiarity panel answers the following questions:
At the top, you can see the level of awareness and familiarity for this piece of information. The awareness bar indicates if people have indicated any form of familiarity, wheres the familiarity bar indicates how familiar people are.
The percentages are relative to the people who hold roles expected to be familiar with the information.
Next comes a list of the people who have indicated their familiarity, including their level of familiarity. Hover over the individual familiarity indicators to view any additional notes given by each user.
If you have indicated your own familiarity, it is displayed at the top of the list:
If there are any people who have roles which are expected to indicate familiarity, but have not done so yet, you can see those people by scrolling to the bottom of the panel:
The primary motivation for indicating familiarity is to keep up with the expectations of the roles assigned to you.
The easiest way to do this is to click the purple "Indicate your familiarity" button which appears in the upper, right corner of your Focus dashboard whenever there are expectations associated with your roles with which you have not indicated familiarity.
You can reach your Focus dashboard by clicking the Wecomplish-logo in the upper, left corner.
When you click the purple button you are taken to the first expectation with which you have not indicated familiarity.
In the top, you will see a familiarity indication section. The left column is for indicating your familiarity, whereas the right column explains why you are expected to be familiar with this piece of information, and your overall awareness of role expectations.
If you want to focus on building familiarity with a particular role, select the role in question from the right column of the Focus dashboard...
...and click the purple "Indicate your familiarity" button in the context of the role:
If you want to indicate your familiarity with an individual role expectation, navigate to the role in question, select the expectation type in the right column, and then click the particular expectation in the left colum.
You can identify which expectations types have missing famiiarity by the first progress bar in the right column being less than 100%, and the expectation in the right column having no familiarity indicator.
For a detailed understanding familiarity, please review Familiarity as a concept and the Familiarity panel.
A piece of insight does not have to be a role expectation for you to indicate familiarity with it.
If you want to indicate familiarity with a random piece of insight, navigate to the page of that insight and trigger the Familiarity panel.
When indicating familiarity, you are only required to select the familiarity level. However, you are encouraged to reflect on and fill out the comments field explaining what's keeping you from reaching the next level of familiarity, as well as deciding on whether you would prefer mentor assistance with improving your familiarity.
Completing these two extra pieces of information makes the familiarity indication vastly more useful both for yourself and your coworkers in identifying the next step to improving your familiarity.
Exploring familiarity can be done in multiple contexts depending on which question you are looking to answer.
If you want to know who is familiar with a given piece of information (and how familiar they are), navigate to that piece of information and open the Familiarity panel.
If you want to know the level of familiarity of pieces of information relative to their siebling, select the "Familiarity" view type in the view type dropdown.
This will display the awareness and familiarity of each individual item, sorted in ascending order first by awareness, and then by familiarity.
The familiarity view type is supported when viewing:
If you want to know how familiar all role holders are with a given role, navigate to that role, scroll down to the "Role holders" section and examine the progress bars located there.
If you want to know how familiar a specific person is with a specific role, navigate to their role assignment.
This can be done either via navigating to that person and their list of roles:
...or via the role and the list of role holders.
If you want to know how familiar a person is with (1) a specific role expectation or (2) a type of role expectations, navigate to that role holder via the person or the role.
If you want to know how familiar a person is with all their role expectations, navigate to that person and examine either their familiarity with (1) overall role expectations or (2) specific skillset expectations.
If you want to know how familiar each individual is with role expectations, navigate to the organizational Familiarity report (Organization > Reports > Familiarity).
If you want to know how familiar the entire organization is with expectations, navigate to the organizational dashboard.
In order for familiarity to be truely useful it needs to be exposed in the context of expectations. That's what the Training view is for.
The training view provides a birds eye view of what a person is expected to familiarize themselves with in order to meet the expectations of a role or skillset, including the progress of that familiarization.
Use cases include:
To access your own training view, click either the "Roles" or "Skills" link in the left hand side navigation, or select the role you would like to train on from the right hand column in the focus view.
You can access the training view of others by searching for that person and clicking the "Roles" or "Skills" links in the left navigation.
Role training is the primary training type, and allows you to train and communicate familiarity in the various expectation types associated with a role.
Allthough skillset training is also a part of roles (provided that the role expects the given skillset), skillset training is also its own thing. This is relevant for those cases where you would like to train in a skillset which is not (yet) required by any of the roles you hold.
Clicking the name of the role or skillset will bring you to the training view. In the context of a role, the training view might look something like this:
In the right column there is a navigation with the different types of expectations associated with the role/skillset, and a percentage indicator displaying your awareness and familiarity for that type of expectation.
The color of the indicator is red between 0% and 33%, yellow between 34% and 66% and green between 67% and 100%.
In the left column there is a list of the specific expectations, including their associated familiary level.
Clicking the name of an item will take you to that piece of content with the familiarization panel open so you can update your familiarity.
Clicking on the purple "Indicate your familiarity" button will take you to the next expectation for which you have not yet indicated your familiarity.
You can see how recently someone has updated their familiarity with their roles, skillsets and individual expectation types in various places:
Indicating familiarity is usually done in the context of role or skillset expectations.
However, you can also update your familiarity with singular pieces of information not neccessarily expected by a given role or skillset.
To update your familiarity with a given piece of information, trigger the Familiarity panel and click the "Indicate your level of familiarity" button, or update the existing familiarity indication.
As a leader or experienced worker, you know that there is a lot of different information which others in your organization would benefit from being familiar with. By making it more clear who is expected to be familiar with what, we can more easily ensure that the right people are exposed to the right information.
Most often the expectation of being familiar with something occurs in association with a role, meaning that we expect a person holding the role to be familiar with certain aspects of the role.
For instance, we might expect someone who is a project manager to be familiar with the responsibilities they are expected to practice, the processes they are expected to contribute to, the risks they are expected to mitigate, etc.
In other cases, we might have particular expectations of certain individuals to be familiar with a particular piece of information.
The platform supports both these use cases, by providing two ways of setting familiarity expectations both for roles and individuals.
Setting familiarity expectations for a role consists of dictating which roles are expected to be familiar with a given piece of information.
This is the preferred method of indicating familiarity expectations, as it will ensure that both existing and future role holders will be exposed to the expectation.
In order to request familiarity via a role, add the roles you would like to be familiar with the information under the "Relevant for" section in the right column of the piece of content.
Requesting familiarity via roles does not produce any specific email notifications to role holders, but rather assumes that users are utilizing the Maintaining familiarity with expectations functionality in order to remain up-to-date with role expectations.
In some cases, you might want to specifically request familiarity from individuals. Use cases include information which does not require familiarity from a given role, but you still want a particular person to be familiar with it.
When you request familiarity, an email is sent to that person. The email contains a link that will take them to the relevant context where familiarity can be set.
To request individual familiarity, open the Familiarity panel, click the "Request familiarity from someone else" button and fill out the form that appears.
When the invitee changes the state of their familiarity, a new email is sent to the person who requested the familiarity notifying them of their familiarity level.
In some cases, you might want to specifically request that someone update their familiarity. Use cases include
When you request an update to familiarity, an email is sent to that person. The email contains a link that will take them to the relevant context where familiarity can be updated.
You might wonder why requesting updates to familiarity isn't triggered automatically by the system.
The reasons for requiring individuals to trigger this manually are:
You can request familiarity from individuals in the following contexts.
If you would like to request familiarity from the people who hold roles which are expected to be familiar with the information, but have not yet indicated familiarity, trigger the Familiarity panel and click the orange bell button in relation to the header "Missing familiarity from".
If you have made significant updates or changes to a particular expectation, it's useful to allow the people who have already indicated their familiarity to familiarize themselves with the updates.
Whenever you edit a piece of information with which people have already indicated their familiarity, you will be prompted whether or not you would like to request a familiarity update from those people.
You can also trigger a familiarity update request manually by opening the Familiarity panel, clicking the "Request an update to familiarity" button and filling out the form that appears.
When you request an update to familiarity, an email is sent to everyone who has already indicated their familiarity requesting them to update it.
If you want to request a familiarity update from a single person, click the allipsis in association with that person and select "Request updated familiarity".
If you would like a person to update familiarity to all the role expections with which they are not 100% aware, navigate to the focus dashboard of that person and click the orange bell button in relation to the "Training and development" heading.
The button only appears if there are role expectations with which the awareness is below 100%.
If you would like a person to update familiarity with their expectations in focus, navigate to the focus dashboard of that person and click the orange bell button in relation to the "Expectations in focus" heading.
The button only appears if there are at least 6 days since familiarity was last updated for any of the expectations.
If you would like a person to update familiarity with the expections of a specific role expectation with which they are not 100% aware, navigate to the role holder view and click the orange button with the text "Request missing familiarity".
The button only appears if there are expectations with which the role holder awareness is below 100%.
As leaders and managers, one of our key responsibilities is to get the best out of our people.
In order to to so, we need to provide them with the training, priorities, and support they need in order to grow and excel in their roles and deliver their best work.
However, executing on this responsibility can pose a lot of challenges:
In order to make it easier to follow up with the people who report to you, the platform provides the My team support view. The goal of this view is to help you answer the question "How can I best support you?" for each of your individual team members.
You can reach the My team view by clicking the Wecomplish logo, and selecting Support Others > My team in the left column.
For each person in your team, you can find a card containing information on how to support them. Here's an example of what a card might look like:
The card is divided into three main sections relevant for reflecting on how to best support that person:
What to expect/look for:
How to act:
What to expect/look for:
What to expect/look for:
Central to the use of the Wecomplish platform is understanding and contributing to the different insight types that can be stored within the platform.
As a result, whenever you're looking to improve your ability to use the platform more effectively and autonomously, it makes sense to focus on improving your familiarity with the different insight types you're expected to contribute to.
To uncover which insight types you're expected to contribute to, navigate to your profile and click the "Explore" button in relation to the Platform box.
This will display the "Only mine" view of the Overview-page, meaning you will only see the insight types the given user is expected to contribute to.
The insight type a person is expected to contribute are those with a light blue background, and where you, on the right hand side, can see either an indication of current familiarity, or an indicator showing that familiarity is missing.
If the insight type is light blue, but the right hand side is empty, the person in question does not have a role in which they are expected to contribute to this information type (yet).
Read more about the Overview-page and how it works here.
To improve your familiarity with a particular insight type, click its name, bringing you to the full view of the insight type.
From here, there are several different options you can choose from in order to better understand how the insight type works.
In order to produce a predictable structure, there are predetermined rules dictating which insight types can be stored under which, and how they can be associated with oneanother.
Read more about how the insight types relate to eachother under the subheading "Understanding the relations" on the Overview-page.
In the white, middle card, there is a "Content" block showing three examples of the insight type published within your organization.
Click one of the items to explore it,or click the "Browse all" button to view more examples.
Reading the documentation of an insight type is a great way to better understand the intention and value of managing a given piece of insight.
Provided that the insight type has an associated documentation page, you can find it by clicking the "How to contribute" button on the white card.
When you feel like you have a conceptual overview, there's no substitute for getting your hands dirty and trying it out yourself.
You can play around with an insight type by publishing, editing and deleting it, either within on of your own teams, or by creating a sandbox team in which you can experiment with diffent insight types.
One of the most common reasons why expectations are not met is because they are not properly understood.
To help identify expectations that are ambiguous, fluffy, confusing or just plain old difficult to understand, the platform implements the concept of unclear expectations.
When Indicating familiarity, the user can check the box indicating an unclear expectation.
This will result in a question mark icon appearing in relation to the familiarity indication, wherever it is visualized.
In addition, unclear expectations are exposed in various views and context throughout the application.
To review which expectations a particular person considers unclear, navigate to that person and click the "Unclear expectations" link in the left navigation, in the "Support me" group.
This will display all the expectations marked as unclear by that person, grouped by type of information.
In order to more easily discover if a person has expectations they consider unclear, the amount of unclear expectations is displayed on their support card.
To review which expectations are unclear within a given team, navigate to that team and click the "Unclear expectations" link in the left navigation, in the "Reports" group.
This will display all the expectations belonging to that team that have been marked as unclear by one or more people.
In order to more easily discover if a team owns expectations that are considered unclear, the number of unclear expectations is displayed on the team dashboard.
To review unclear expectations at an organizational level, navigate to the organization and click the "Structural capital" link in the left navigation, under the "Reports" group.
This will display all unclear expectations divided by team, including links to the unclear expectation report of each individual team.
Most of us have lots of development potential. The indication of familiarity helps expose this fact, but can also make it feel overwhelming to get started improving ones familiarity ("Where do I start?").
In order to make the development process more tangible, better aligned with others perception of our potential and to enable us to better prioritize, the Platform uses the concept of expectations in focus.
Think of expectations in focus as providing you with a method for addressing the concept of people working with themselves in the context of a role. You can hear this referred to in day-to-day chatter as people saying "I'm working on that" or "He really needs to work on that".
With focus we can signal which specific expectations (be it a responsibility, a skill, etc) a person is expected to prioritize their development efforts towards. Put another way, we can communicate which expectations a person is expected to improve their familiarity with.
Focus can be set by the familiarity holder themselves, or by another person suggesting something that that person might benefit from focusing on.
There are two ways in which you can set something in focus:
To set focus on an expectation navigate to that user, make sure the "Expectations" tab is selected and click the "Add expectation" button.
This opens up a search field in which you can search for the expectation you would like to be put into focus.
Start a check-in. When you get to the expectations step, click the "Add expectation" button.
This opens up a search field in which you can search for the expectation you would like to be put into focus.
Navigate to the expectation.
If you want to set the expectation in focus for yourself, click the pin-icon to the right of the familiarity indicator. Click again to disable focus.
If you want to set the expectation for someone else, toggle the familiarity panel and click the focus indicator corresponding with the person you want to focus on it.
Please note that this way of setting familiarity only works if the person has already indicated their familiarity. If the person has not indicated their familiarity yet, you can work around this by first setting the familiarity expectation for that individual, and then set focus on that expectation.
To prevent the expectation of focusing on too many things at once, a person can only have 5 expectations in focus at the same time.
If you attempt to set items in focus for a person who already has 5 items in focus, you will receive a warning and focus will not be set.
In order to view which expectations a person is focused on improving, navigate to the Focus-dashboard for that person. The expectations in focused are displayed under the "Expectations" tab of the Priorities-section, which is visible below the Plans-section in the left column.
To review the focus of multiple individuals at the same time, use the Focus report.
In the beginning, it can feel foreign and difficult to identify which things to put in focus. Consider using one or more of the following methods for identifying relevant expectations:
As you grow more familiar with the expectations in focus feature, so will your intuition for discovering and pinning expectations whenever you realize that there's something you would benefit from improving your familiarity with.
As a reminder to keep checking in with and reflecting over the expectations you have in focus, a purple play button appears at the top of your expectations in focus whenever you have one or more expectation with which you have not updated your familiarity the last 7 days.
Click the button to be taken through each pinned familiarity indication older than 7 days.
You can also use Check-in (one-on-one) to ensure that you maintain focus on both your expectations and other priorities.
The first time someone completes indicating familiarity with all the expectations of a specific role or a skillset, an email notification is sent out to key stakeholders.
The purpose of the notification is two-fold:
For role familiarity completion, the following people are notified, if specified:
For skillset familiarity completion, the following people are notified, if specified:
The role list and single role view for a person includes charts indicating how that person is developing over time. In the context of the Platform, development is measured as a change in familiarity with role expectations.
There are two charts indicating changes in awareness and familiarity respectively. They are displayed at the top of the role list of a person, and at the bottom of the single role view of a person.
Each chart has two Y (vertical) axis.
The left axis corresponds with the purple line and displays the score over time. This number is always expected to grow unless someone deletes or downgrades their familiarity.
The right axis corresponds with the green line and displays the percentage over time. This number will increase when familiarity is set/upgraded and drops when additional expectations are added to the roles assigned to that person.
We could all benefit some guidance and well-meaning nudges in order to progress in our roles and better master a skillset. And it's not neccessarily always our leader who is the best fit for this job.
To produce this type of social support and accountability, the platform implements the concept of mentors.
A mentor is someone who aims to provide someone else (the mentee) with intellectual and emotional support in an attempt to improve their understanding of and familiarity with a given role or skillset.
In order for the mentor/mentee relationship to work properly there needs to be an awareness of the relationship and regular communication between the two parties.
A mentor is responsible for helping the mentee, by:
In turn, the mentee should:
A mentor can be allocated to any specific role or skillset assignment of a person.
To assign a mentor, select the role/skillset in the training context of a given user and select a mentor in the right hand column.
If you check the box "Send notification", an email will be sent to the mentor notifying them of the mentorship expectation and linking them to this documentation in order to improve their awareness of the mentorship concept.
A list of the roles and skillsets a person is mentoring others in is availble under the Mentorships menu item.
If you require outside assistance in order to improve your familiarity with something, check the "Request mentor assistance" checkbox when indicating familiarity.
This will result in a life ring icon appearing in relation to your familiarity indication, wherever it is visualized.
Mentors can easily see which mentees require assistance (and for which expectations) from their mentorship overview.
For roles invested in making sure that there exists an network of mentors to help and produce accountability (CEO/insight manager/training and development manager), there exists an overall mentorships report. The report is only accessible to platform admins.
To view the report, go to Organization > Report > Mentorships.
Here's an example of a report:
Use the report to ensure that:
In order to make sure that familiarity data is presented quickly, and to report on Development over time, a persons awareness and familiarity with roles is cached. The cache means that a persons familiarity with roles does not have to be calculated with each page load.
The cache is used the following places:
The cache is automatically rebuilt when:
There are cases where the cache can grow outdated. Most commonly this happens when new expectations are added, and none of the automatic triggers for cache rebuilding has occured since.
Outdated cache can most easily be recognized on the Roles-list of a person, where the left column list of roles is uncached, and the right column list is cached.
If you suspect that the cache is outdated for a given person, you can manually trigger an update of the cache by clicking the refresh icon in the right column of the Focus-dashboard, or in the Role familiarity report.
Using the functionality for roles and responsibilities you can clearly communicate and manage
Roles are intended to function as living, up-to-date job descriptions which gradually evolve as the role holder and organization in general learns more about what the responsibilities should entail and how to operationalize them.
By making proactive use of the role functionality, roles and responsibilities are easily redistributable as the organization grows and adapts.
Here's an example of how a role might appear:
Roles are created in the context of a team. To create a role, click the plus icon in the upper, right corner and select "Role", or use the keyboard shortcut "r".
You can assign a role to a person by navigating to that Person > Roles and adding the role.
You can also assign a person to a role by navigating to the role in question and add the person as a role holder. The effect of assigning a role to a person and a person to a role is the same.
The remainder of this documentation is focused on assigning roles to a person.
When assigning roles to a person, you can either select from the list of pre-existing roles, or have a new role created.
If you type in the name of a role which does not already exist, the role is created for you. If your organization consists of multiple teams, you will be prompted to select the team which is expected to maintain the role.
In order to select a pre-existing role, start typing into the role name field in order to get an autocomplete list of existing roles matching your query within your organization.
To see all roles, click the "Browse all" link in the right corner to expand the available role options. This expands not only the list of roles within your own organization, but also the roles that publicly available within the Wecomplish Library.
The following states are available for the role assignment:
You can see all your own roles and their current state by selecting the view of you role, or see all the roles of a coworker by searching for that user which will bring you to their role page.
If the role assumes certains skillsets in order to comply with quality expectations and regulations, you can add skillset expectations to the role.
To add a skillset expected of a role, navigate either to the role in question and add the skillset expected:
...or navigate to the skillset in question and add the role which expects it:
When adding a skillset expectation, you are asked to select the minimum level of proficiency expected. Hover over the question marks to get a detailed explanation of how each proficiency level is defined.
Once you are done specificing which skillset you expect of which roles, and at which level, use Skillsets with insufficient proficiency to collect information about how well someone masters a skillset and identify where people need to improve.
Responsibilities are primarly managed in the context of a role. If you're not sure who holds (or should hold) the responsibility, you can create an unmanaged responsibility directly on the team.
Each responsibility has a given frequency (or alternatively "ongoing") explaining the expectation of how often the responsibility should be adressed.
The responsibilities are grouped by category when displayed. Here's an excerpt of the list of responsibilities from the team leader role:
Assigning someone to a role does not automatically ensure that the associated responsibilities are adhered to. People are busier than ever, so unless a responsibility has been properly automated as default behaviour, it can quickly be forgotten.
Use recurring allocations to make sure that a given individual has reserved time for a given responsibility.
The avatars in the list of responsibilities indicate which users (if any) that have recurring allocations for a given responsibility.
Click into the responsibility to see details of the associated recurring allocations.
For organizations expected to grow into new markets and countries, it makes sense to reuse roles and responsibilities across different markets/countries.
In order to be able to do this, you should aim to maintain market/country neutral roles, and rather indicate country/market as a part of the team in which the role is assigned.
Here is an example of a role that is market/country specific:
And here is that same role, reorganized to be market/country neutral:
This example applies specifically to roles and responsibilities, but the same goes for skillsets, processes and other types of structural capital that might be relevant to reuse in different markets/geographical locations.
As roles and their associated responsibilities grow in size, the amount of responsibilities can make it more difficult to gain an overview of the role and, as a result, maintain role clarity.
To preserve role clarity of a growing role you can categorize the responsibilities that naturally fit togheter. Categorizing a responsibility is done by clicking the name of the responsibility and managing the categories in the right column.
The result of categorizing responsibilities with the same category is that the appear together in the list of responsibilities.
In the context of role familiarity, categorizing responsibilities has the added value of accumulating familiarity pr category. By selecting "Familiarity" in the dropdown and clicking "Collapse categories", you can more easily analyze which categories of responsibilities a role holder is more and less comfortable with.
Ferdighetssett (skillsets) hjelper teamet å få oversikt over hva man forventes å kunne for å levere effektivt i en eller flere roller på teamet, og hvilke personer som besitter hvilke ferdighetssett.
Ferdighetssett er en samlebetegnelse på et sett med ferdigheter som gjør at man ville svart "ja" når noen spør deg om du kan ferdighetssettet.
"Føre regnskap" og "Spille gitar" er eksempler på ferdighetssett.
For å legge til et ferdighetssett, gå til teamet hvor ferdigheten forventes, velg "Kompetanse" i menyen og trykk på "Nytt ferdighetssett".
For å se personer som mestrer et ferdighetssett, klikk deg inn på ferdighetssettet.
Her kan du se alle som mestrer ferdighetssettet, sortert kronologisk etter når de begynte å praktisere ferdighetssettet.
For å legge til flere personer som mestrer ferdighetssettet, trykk på "Legg til person", søk opp personen det gjelder og angi når vedkommende begynte å praktisere.
Du kan se alle ferdighetssettene en person mestrer ved å trykke på vedkommendes navn i listen over personer, eller ved å søke opp vedkommende og velge "Kompetanse" i navigasjonen.
A skillset is something that someone can be considered proficient in (aka "good at"). Playing guitar is a skillset. The same is Cold calling a prospective client.
In order to identify if something is a skillset, try asking the following questions:
If the answer to at least one of the above questions is "yes", then you are probably dealing with a skillset.
Skillsets are broken down into the particular skills on is expected to be able to perform/know in order to be considered proficient in the skill. Skills can be broken down into subskills where neccessary.
In the context of the Playing guitar skillset, skill examples might include
Skillsets are sometimes confused with the closely resembling information types skills and policies.
Here's how to think about these three information types in order to better distinguish between them.
Describes expected proficiency/level of mastery. Collection of singular skills.
Describes a singular ability one is expected to be familiar with in order to be considered proficient in the parent skillset.
Describes expected behaviour.
When associating a skillset with a role, you can select which level of proficiency is expected of the role holder.
This makes the platform able to expose which the skillsets in which a person has insufficient proficiency, based on their roles.
Information about insufficient proficiency can be used to:
To get to the insufficient proficiency view for an individual, navigate to that individuals Focus dashboard and click the "Unmastered" indicator in the right column.
To get to the insufficient proficiency view for a team, navigate to that team and click the "Unmastered" menu item in the left column.
The report displays all the skillsets insufficiently mastered by the individual, grouped by the roles expecting them.
For each skillset you can see the expected proficiency on the left, and the current proficiency on the right. You can also see by whom the current proficiency has been set.
If no proficiency is set yet, a purple "Indicate proficiency" button is displayed. Click it in order to indicate proficiency.
The list only includes the skillsets in which the person is insufficiently proficient. Once a sufficient proficiency-level is set, the skillset is removed from the view.
The report displays all the skillsets insufficiently mastered by the role holders of the roles owned by the team.
For each skillset you can see the expected proficiency on the left, and the status of the current proficiency on the right.
The current proficiency is broken down into three numbers:
People take a lot of pride in what they know, which means that dictating proficiency can sometimes be a delicate process.
We recommend that two people sit down together to discuss and set proficiency for a person. Ideally these two people are the one who is expected to master the skillsets, and a person who has observed them practicing the skillsets.
This enables a discussion around which level of proficiency the role holder is currently at.
In cases of disagreement on proficiency, calibrate yourself towards the familiarity indicated by that person. You can see the familiarity of the skillset by clicking the name of the skillset. Here are some guidelines for how to align proficiency with familiarity:
To copy a skillset, click the edit-button in the upper right corner and select Copy.
Skillsets can be copied to a different team. If you want to copy a skillset to a different organization, your user needs access to both the organization currently holding the skillset, and the destination organization.
When skillsets are copied, it's the skillset and underlying skills that are copied. Associated content like roles expected to master the skill or content related to a particular skill is not copied.
In the platform, ambitions represent people's overall and long-term desires to get better and produce more value.
Working towards our ambitions should give us a sense of fulfillment and accomplishment, and make us better at practicing the roles we would like to hold, both now and in the future.
Compared to the concept of objectives, which are team-specific, ambitions are personal, meaning they relate to an individual's growth and development potential.
Compared to the concept of Expectations in focus, ambitions are more holistic, less granular and are expected to take longer to develop. Picking specific expectations in focus from ambitions is, however, one concrete way of working towards an ambition.
The ambitions of someone can be associated with
You set something as an ambition by clicking the seedling indicator near the current state og the role or skillset assignment in question.
Setting an ambition can be done from the following views:
If you set something as an ambition of someone else, you will receive a Notification of completed familiarity.
When setting something as an ambition, it is displayed in the on the Ambitions tab of the priorities widget on the Focus-dashboard.
The view includes the roles and skillsets set as ambitions, including their current state and their mentors (if any).
As leaders, we have a responsibility to identify and communicate to our team what well-functioning looks like, and evaluate how well each individuall stacks up to those expectations and best practices.
To help leaders practice this responsibility, the platform provides the Evaluation information type.
Evaluations helps us reflect, learn, understand and make better decisions by collecting people's opinions on how someone currently stacks up, and to which extent they are expected to be able to improve.
The platform supports the evaluation of people and their ability to master and improve in practicing different roles, skillsets and values.
Some use cases of evaluations include:
When we are looking to grow and develop ourselves or others, there's potentially an infinite number of places we could start.
This can present some issues:
To cut down on the number of options and better identify where our potential is the greatest, the platform uses the concept of assessments.
An assessment is a high-level, opinionated perception of how well someone masters something (i.e a role or a skillset), and how impactful we would expect it to be if they were given the proper development opportunities and applied themselves.
Assessments are meant to help people systematically collect input on potential from both themselves and others, and use that information to prioritize their development efforts.
Use cases for assessments include:
Assessments bear some resemblance to other, neighbouring development concepts, like ambitions, familiarity and proficiency. Here's how assessments differ from:
During an assessment, the person doing the assessing is asked to evaluate someone's current performance and the expected impact of improvement if that person were given the proper development opportunities and applied themselves.
Based on these two primary factors, the system calculates a person's potential. The calculation looks like this:
Potential = Impact + (Impact - Performance)
The different performance and impact options are assigned the following values in the calculation:
Here's are a couple of calculation examples:
Someone's is considered to be performing Well (2) in a role, with a Limited (1) improvement impact. Their potential is calculated as 1 + (1 - 2) = 0.
Another person is considered to be Moderate (1) in a particular skillset, with a High (3) improvement impact. Their potential is calculates as 3 + (3 - 1) = 5.
To assign meaning to the outout of the calculation, they resulting scores are grouped into the following labels:
The setting and measuring of goals in the Wecomplish platform is built around the universal goal-setting framework OKR.
OKR us short for Objectives and Key Results and is a methodology ideal for defining and tracking objectives and their outcomes in agile teams.
An OKR is made up of an objective - a clearly defined goal - and specific measures used to track the achievement of that goal. The goal of OKR is to define how to achieve objectives through concrete, specific and measurable actions.
Here's an example of what an OKR looks like in Wecomplish:
Objectives are managed in the context of a team to promote aligning OKRs with the teams purpose. To create a new objective, navigate to the team and select OKR in the left hand side navigation or use quick create.
The objective can be in one of the following states:
By adding initiatives you raise awareness of how work is associated with objectives as well as increase the likelihood of work actually being aligned with objectives.
Initiatives can be pre-existing projects or tasks defined in the platform. Items added as initiatives display their related objectives on the reverse side.
By adding an owner, responsible and contributors you make it clear who is expected to hold which role in the achievement of the objective.
The people you add you add will see their objectives, grouped by their role, in their "Planned work" view.
By adding key results you make it more clear how the team plans to measure the achievement of the objective.
Each key result has a current and target performance expectation, making it clear and measurable to which extent objectives are met.
The OKR methodology comes with the following recommendations for key results:
The platform suports tracking progress on key results, so that we can more easily follow how close we are to achieving the result.
Progress is typically reported by the person responsible for the objective, making it easily available to all other objective stakeholders.
To track progress on a key result, click the key result and then click the green plus-icon in relation to the Progress-header. Progress is indicated by a percentage of the target for the key result (aka fulfillment).
When viewing an objective, the list of key results includes a progress bar of the most recent progress indication.
Key results can be manually sorted in the order you would like. This can be useful if the nature of the objective makes is natural to tackle one key result at a time, in a specific order.
Click and drag the hamburger-icon on the rigth-hand side of a key result in order to give it its preferred priority.
Objectives come in different shapes and sizes. Some are high-level and long-lasting (aka North Star Objectives), whereas others are more concrete, shorter lived and exist primarily to impact higher level objectives.
For instance, a product team objective of improving self-service abilitites and a sales team objective of closing x deals within the quarter might both be designed to impact a higher level Annual Recurring Revenue objective.
Ideally, any objectives we set out to accomplish can somehow be associated with on or a select few top level objectives.
In order to better understand how objectives are meant to impact eachother, the platform allows for relating objectives to other objectives they are expected to impact.
Relating objectives is done under the "Related objectives" section in the right column of an objective.
When relating objectives you decide if you want to relate objectives that are:
If you are looking to break down a big and unmanagable objective into smaller objectives that can be more easily managed, the Sub objectives function might be a better fit.
To view all active, related objectives across the entire organization, check out Organizational objectives.
Some objectives are too big to tackle on their own, or for any one person to be responsible for. In order to break more complex objectives into smaller, more managable objectives, use the sub objectives. Sub objectives allow you to create a hierarchy of objectives however deep you would like.
If you are looking to break up a high level objective into more concrete objectives managed by different teams, the Related objectives function might be a better fit.
The Organizational objectives overview allows us to:
The report displays all objectives across all teams that are either in the planning or focusing stage.
The report takes Related objectives into account, indenting objectives that impact eachother under eachother. The top level objectives (after taking related objectives into account) are grouped by team.
The right column includes a team-navigation displaying which teams own how many objectives in the current view. By clicking on the team name, the objectives owned by that particular team light up.
Ideally, every active team objective is tied to a more high-level objective on the organizational level. You should therefore strive to have only the team representing the organization appear as a group in the left column.
If you have multiple team groups appear, it might be an indication that the impact of those objectives on higher level objectives are poorly understood, or worse yet, that the objective is not designed to impact a higher level objective (in which case it should probably be abandoned).
KPI-er (Key Performance Indicators) er indikatorer som vi er opptatt av hvordan presterer, og som vi handler på når prestasjonen faller utenfor det vi definerer som et akseptabelt intervall.
En KPI type er en type viktig forventning med logiske regler knyttet til seg som lar systemet automatisk samle informasjon om KPIens prestasjon. Unntaket er KPI typen "Manuell" hvor prestasjon må legges inn manuelt.
Se underlagte artikler for informasjon om de enkelte KPI typene.
Måler andelen (i prosent) av timene brukt for et budsjett.
Følgende informasjon overstyres automatisk for KPI-typen (og innhentes derfor ikke):
Følgende informasjon innhentes i tillegg til øvrige KPI-er:
Måler hvordan resten av det pessimistiske estimatet for et prosjekt presterer ift rest budsjett (for å vurdere om budsjettet vil strekke til).
Følgende informasjon overstyres automatisk for KPI-typen (og innhentes derfor ikke):
Følgende informasjon innhentes i tillegg til øvrige KPI-er:
Måler andelen (i prosent) av oppgavene i et prosjekt som er utført, basert på oppgavenes estimat.
Følgende informasjon overstyres automatisk for KPI-typen (og innhentes derfor ikke):
Følgende informasjon innhentes i tillegg til øvrige KPI-er:
Årsaken til at man velger budsjett og ikke prosjekt som relasjon er at det er budsjettet som holder på første og siste leveransedato, som trengs for å beregne forventet fremdrift.
Teller antallet observasjoner en bruker har registrert manuelt i rapportperioden, og deler disse på antallet timer arbeidstid ført i samme periode. Arbeidstid er tid med en av følgende lønnsarter:
Brukeren velges ved å søke opp vedkommendes navn i feltet "Owner" når man oppretter KPI-en.
Beregner automatisk work in progress (på tidspunktet hvor rapporten opprettes) for en bruker ved å legge sammen realistiske estimater for oppgaver som er åpne, som har nådd implementering eller lenger, og som brukeren har ansvaret for.
Brukeren velges ved å søke opp vedkommendes navn i feltet "Owner" når man oppretter KPI-en.
Typen Manuell har ingen spesiell logikk knyttet til seg og forutsetter at du beregner KPI-prestasjonen på egen hånd.
Følgende felter nyttegjøres:
Du kan se prestasjonen for en KPI ved å klikke deg inn på den relevante KPI-gruppen, og deretter inn på den aktuelle KPI-en.
For å opprette en ny prestasjon for et sett med KPI-er, trykk på "Ny rapport" øverst til høyre inne på KPI-gruppen som inneholder KPI-ene du ønsker å legge inn prestasjoner for.
Dersom prosjektet eller KPI gruppen består utelukkende av automatiske KPI typer vil prestasjoner legges inn automatisk og "Ny rapport" lenken vises ikke.
KPI-er organiseres i KPI grupper. En KPI gruppe er en samling med KPI-er som har en sammenheng, og som rapporteres på med samme frekvens. En rapport er en gjengivelse av KPI-enes faktiske prestasjon for en gitt periode.
I listevisning gjengis KPI-gruppen med gruppens navn, samt navn og helhetlig prestasjon på siste rapport. Helhetlig prestasjon gjenspeiles med en prikk med en farge, som signaliserer følgende:
En KPI gruppe kan ha en bestiller, en produsent og en ansvarlig. Mine KPI-er gjengir KPI-ene man har en eller flere roller.
For KPI-er som presterer utenfor akseptabelt intervall opprettes det automatisk en observasjon.
Dersom KPI gruppen har en bestiller og en ansvarlig settes bestiller som observasjonens innmelder og ansvarlig som observasjonens ansvarlig.
Dersom roller ikke er definert for KPI gruppen settes rapportutformer som innmelder når rapporten opprettes.
Dersom observasjonen har en ansvarlig settes observasjonen direkte til Ny, hvis ikke settes den til Kartlegges.
Observasjoner som ikke automatisk får en ansvarlig settes til kundeansvarlig for teamet.
Prestasjoner (aka Accomplishments) er ting du føler du selv eller noen andre har fått til.
På "Mine prestasjoner" siden ser du prestasjonene du er en bidragsyter til, sortert synkende etter når de ble opprettet.
Du kan velge for hvilket datointervall du ønsker å se prestasjoner. Standard datointervall er inneværende uke.
Prestasjoner støtter Kommentarer.
Gå til Meg > Prestasjon > Prestasjoner > "Ny prestasjon" eller nyttegjør Add new information.
En prestasjon kan knyttes til flere bidragsytere. Når du oppretter en prestasjon blir du automatisk lagt til som bidragsyter.
Du kan se andre brukeres prestasjoner ved å søke opp brukerens navn og velge "Prestasjoner".
Når du legger til en annen person som bidragsyter vil denne personen bli gjort oppmerksom på prestasjonen i form av et varsel til innboksen.
Checking in with stuff is a big part of management, collaborating, achieving goals and operating an organization in general.
Nearly all teams develop some sort of check-in scheduele over time to ensure that things run smoothly.
Check-ins help us:
Some check-in patterns that commonly develop in teams over time are:
Commonly, check-ins are organized as meetings amongst team members. This may or may not result in an effective check-in.
It all depends on whether:
To help alleviate these potential pitfalls, the platform supports health checks.
Health checks allow you to organize and share your thinking around who should check in with what, why, at which intervals and how. Health checks also allow you and your team to log actual check-ins with a health check, making it easier to share the information uncovered, agreements made, as well as ensuring that the health checks are actually being conducted.
Each health check is broken down into perspectives. Perspectives are the different aspects you want to look at when checking the health of something.
For instance, if the focus of a health check is projects, some relevant perspectives might include:
For each perspective, you can share insight around which data to review and which questions to ask in order to best evaluate the perspective.
Policies are a great way of sharing and aligning preferred team behaviour.
A policy consists of
In order to add a new policy, use the quick create functionality or navigate to the relevant team, select Policies and click the green plus icon.
Policies can be categorized in order to group similar policies together. Policies are grouped by their categories when displayed in the context of the team.
Linking policies to roles help ensure that people remain familiar with relevant behavioural expectations as the organization grows and policies adapt.
Linking a policy to a role is what ensures that the policy appears in the training view for that role.
A policy can have one of the the following states:
The current stat of the policy is displayed to the right of the policy title.
Sjekklister er den etablerte/offisielle måten å gjøre noe på.
Sjekklister knyttes til et team og består av et hierarki av deloppgaver som kan påføres nye eller eksisterende oppgaver.
Teamets sjekklister er som et utgangspunkt kun tilgjengelig for brukere som har tilgang til teamet.
Unntaket er dersom du har valgt å Gjøre en sjekkliste tilgjengelig i biblioteket.
You may use the quick create functionality or navigate to the relevant team, select Checklist in the left menu and click the green plus icon in the up-right corner.
Oppretting av nye oppgaver i en sjekkliste fungerer på samme måte som oppretting av nye deloppgaver.
Du kan endre en oppgaves plassering i oppgavehierarkiet ved å dra og slippe oppgaven til ønsket plassering. Dersom du ønsker å plassere en oppgave dypere i oppgavehierarkiet, klikk på tallet som indikerer antallet underlagte oppgaver for å å åpne opp det relevante hierarkiet.
Vi kaller informasjon om oppgaver i sjekklister for meta data. Meta data er informasjon du ønsker at enten skal kopieres inn i oppgaven når sjekklisten opprettes, eller på en annen måte hensyntas når sjekklisten påføres.
Oppgaver i sjekklister støtter følgende typer metadata:
Personen du ønsker skal tildeles oppgaven når sjekklisten påføres.
En beskrivelse du ønsker kopiert inn som oppgavebeskrivelse når sjekklisten påføres.
Signalisering av at en oppgave er blokkert av en annen. Når sjekklisten påføres vil blokkerne knyttes mellom oppgavene som opprettes.
Et etimat du ønsker kopiert inn som oppgave estimat når sjekklisten påføres.
Signalisering av at en oppgave har en frist. Når sjekklisten påføres vil du bli bedt om å angi de konkrete fristene for oppgavene.
Signalisering av at en oppgave skal innlemme en annen, frittstående sjekkliste. Når sjekklisten påføres vil den frittstående sjekklisten kopieres inn på rett plass i oppgavetreet.
Etter du har redigert eksisterende metadata vil du bli spurt om du ønsker at endringene skal forplantes til åpne oppgaver.
Når du legger til eller endrer metadata vil du, dersom det finnes åpne oppgaver basert på sjekklisten, bli spurt om du ønsker å oppdatere disse oppgavene med sjekkliste-endringene.
Det er støtte for å forplante følgende typer meta-endringer:
Du bruker en sjekkliste ved å påføre den på et prosjekt eller en oppgave.
En påføring vil si at sjekklisten brukes som mal for å opprette et oppgave-tre hvor det er mulig å kommentere, føre fremdrift, logge tid og skape annen sporbarhet i gjennomføringen av arbeidet.
Du kan påføre sjekklister på forskjellige måter på forskjellige steder:
Dersom sjekklisten som påføres har oppgaver med meta data som krever input vil denne inputen bli etterspurt når du påfører sjekklisten.
Følgende meta data krever input:
En prosdyre kan innlemme andre sjekklister.
Dersom en av sjekklistene som er innlemmet mangler på påføringstidspunktet vil du bli varslet om dette slik at du kan velge om du ønsker å opprette/kopiere inn sjekklisten, eller fortsette påføringen uten den innlemmede sjekklisten.
Det er mulig å eksportere punktene i en sjekkliste til en issue i den utbredte issue trackeren Jira.
Eksporten oppretter deloppgavene i sjekklisten som subtasks i Jira, med e-postadressen til den innloggede brukeren i NM Project som reporter.
Ettersom Jira ikke støtter et hierarki av subtasks vil sjekklister bestående av et hierarki som et utgangspunkt innlemmes deloppgaver på nivå 2 og dypere som oppgavebeskrivelser.
Krysser du imidlertid av for "Lag deloppgaver på alle nivåer" så ville alle deloppgaver i hele hierarkiet konverteres til en flat deloppgavestruktur.
Eksempelvis vil følgende sjekkliste
Mor
Barn 1
Barn 2
...importeres inn som følgende to subtasks:
For å kunne eksportere sjekklister til en Jira issue må du sette opp et eller flere Jira prosjekter. Det finnes i dag inget grafisk grensesnitt for å legge til Jira prosjekter. De må redigeres direkte i databasen, i tabellen JiraProject.
For team med mange sjekklister kan du kategorisere disse. Sjekklistene vil grupperes på kategoriene på teamets liste over sjekklister.
For å kategorisere en sjekkliste, gå inn på sjekklisten og trykk på "Legg til kategori".
Skriv inn ønsket kategori-navn og trykk på Legg til. Dersom du har lagt til kategorier tidligere vil det å begynne å skrive et kategorinavn søke blant disse.
I høyre kolonne, under deloverskriften "Påføringer", kan du se hvor, når og av hvem sjekklisten har blitt påført.
Du kan også klikke deg videre ut til prosjektet eller oppgaven sjekklisten har blitt påført om du ønsker å studere nærmere hvordan arbeidet har blitt gjort.
Sjekklistene er organisert i grupper basert på hva de er tagget med. Sjekklister uten tags vises først.
Bruk det globale søket for å søke opp sjekklisten ved navn.
Du kan flytte en sjekkliste til et annet team ved å trykke på ikonet av et hus i tilknytning til brødsmulestien, eller ved å nyttegjøre tastatursnarveien Cmd + Shift + P.
Dette vil utløse en modalboks hvor du kan søke opp teamet du ønsker å flytte sjekklisten til.
En sjekkliste kan ha forskjellige tilstander som gjenspeiler forventningene til sjekklistens bruk. De alternative tilstandene er:
Nye sjekklister som opprettes får automatisk tilstanden "Utkast". Det er kun sjekklister med tilstanden "Aktiv" som forventes nyttegjort. Når sjekklister ikke lenger er i bruk settes de til tilstanden "Arkivert".
For å endre en sjekklistens tilstand, klikk på pilen som peker ned ved siden av tilstandsangivelsen i toppen av sjekklisten i fullvisning og velg en ny tilstand.
Du kan kopiere sjekklister du har tilgang til å se. Et use case for å kopiere en sjekkliste er dersom en annen organisasjon som bruker Wecomplish har en sjekkliste som du ønsker å kopiere til et av dine egne team.
For en nærmere forklaring, se Dele innhold på tvers av organisasjoner.
Dersom du ønsker å dele en sjekkliste med andre utenfor din organisasjon kan du gjøre den tilgjengelig i Dele innhold på tvers av organisasjoner.
For å gjøre sjekklisten tilgjengelig og søkbar i biblioteket, rediger sjekklisten og kryss av for "Offentlig tilgjengelig" og velg en kategori som sjekklisten skal presenteres under i listen "Offentlig kategori".
The platform allows you to create a wiki for a team or a project in the form of pages organized in a hierarchy with associated Kommentarer. The pages support rich formatting, familiarity and are searchable in the global search.
By default, the wiki is only accessible to logged in users who have access to the team or project with which the wiki is associated.
However, by editing the team and checking the "Make wiki publicly available" option, the wiki is made available to anyone on the internet, without having to log in.
Look for this indicator to see if the wiki page you're currently working on is a part of a publicly available wiki:
For å endre rekkefølgen på sider, dra og slipp sidene i ønsket rekkefølge. Du kan kun endre rekkefølgen på sider underlagt siden du befinner deg på.
For å endre en sides plassering, trykk de tre prikkene øverst til høyre og velg "Flytt".
En sides forelder kan være et team, et prosjekt eller en annen side.
Dersom du ønsker å motta varsel om endringer i et teams wiki må du abonnere på dette.
For å opprette et abonnement, naviger deg fram til den delen av wiki-en du ønsker å bli varslet om endringer for og trykk på knappen "Varsle meg om endringer" i høyre kolonne.
Når du har aktivert varsling endres knappen til "Ikke varsle om endringer". Trykk på denne om du ønsker å skru av abonnementet igjen.
Et abonnement gjelder for siden du abonnerer på (direkte abonnement) og alle underlagte sider (indirekte abonnement).
Det betyr at et abonnementet du oppretter på wiki-forsiden vil resulterte i et indirekte abonnement på hele teamets wiki, mens et abonnement opprettet på en konkret side kun vil resultere i indirekte abonnement på sider underlagt denne.
Ansatte kan, i tillegg til å styre eget abonnement, legge til og fjerne andres abonnement på wiki-en.
Administrasjon av abonnementer gjøres ved å trykke på teksten i høyre kolonne som viser hvor mange som abonnerer på denne delen av wiki-en.
Fra dette vinduet kan du legge til nye abonnenter og fjerne direkte abonnement. For indirekte abonnement gjengis det en lenke til hvor det direkte abonnementet har sin opprinnelse.
For å varsle om en endring i wiki-en, kryss av for "Varsle om endringen" når siden redigeres. Dette vil sende ut en e-post om tekstendringene på siden til alle med direkte og indirekte abonnement på siden. Trykk på teksten som viser hvor mange som varsles om endringer for å se de konkrete personene som vil motta varsel.
Om du også fyller ut feltet "Motivasjonen bak dokumentasjonsendringen" vil denne forklaringen inkluderes i e-postvarselet. Feltet støtter Rik formatering.
Ved opprettelse av en side har du muligheten til å velge en mal som siden skal kopiere innhold og eventuelle underlagte sider fra.
Les mer om Maler.
There are multiple places where you can upload images and other types of attachments which can then be embedded into rich text areas.
These are the insight types that can be assigned attachments. In addition, attachments can be added to comments on tasks and observations.
Press the button or link labeled "Upload attachment". Select the attachments you want to upload by clicking the "Browse" link, or by dragging and dropping the relevant files to the upload area.
Then, click the "Upload x file" button in order to actually trigger the upload. When you are done, you can close the upload widget by clicking the cross in the top, right corner.
Med maler kan teamet definere utgangspunkt for enkeltsider og hele hierarkier av dokumentasjon slik at teamet kan spare tid og tydeliggjøre forventningene til hvordan noe forventes dokumentert.
En mal kan ha et innhold og x antall undersider ordnet i er uendelig hierarki.
En underside kan innlemme andre maler slik at én mal kan gjenbrukes på tvers av flere maler, uten at innholdet må vedlikeholdes flere steder.
For å opprette en mal, gå til teamet, velg Maler i navigasjonen og trykk "Ny mal".
Teamets maler er som et utgangspunkt kun tilgjengelig for brukere som har tilgang til teamet.
Unntaket er dersom du har valgt å Gjøre en mal offentlig tilgjengelig.
Du kan kopiere maler du har tilgang til å se. Et use case for å kopiere en mal er dersom en annen organisasjon som bruker Wecomplish har en mal som du ønsker å kopiere og tilpasse for et av dine egne team.
For å kopiere en mal, velg "Kopier" i listen over handlinger tilknyttet en mal. Du vil så få velge hvilken organisasjon og hvilket team malen skal kopieres til.
Dersom du ønsker å dele en mal med andre utenfor din organisasjon kan du gjøre den offentlig tilgjengelig.
For å gjøre malen tilgjengelig, rediger malen og kryss av for "Offentlig tilgjengelig".
Processes are a great way to describe what a team or an organization is expected to be able to do, and which resources are required to complete each step in the process.
A process consists of a tree of process steps, tied together with optional conditions, to form a complete process.
Each process step can be associated with the resources relevant to complete that step, be it roles, systems, checklists, policies, risks, etc.
In addition to their ability to communicate how something is done, the process implementation in the platform is also tactical, meaning processes can be applied across projects and tasks.
When you want to utilize a process, you can apply it to a project or a task.
Applying the process provides multiple benefits, including:
To apply a process, navigate to the process and click the green plus icon in relation to the Applications heading.
Applying a process brings you to the step selector. Here you decide which of the available steps to apply, and where to apply it.
When triggering a process application the initial process step is the only option, and you are prompted to select a location (project or task) to which the process should be applied.
After selecting a step, you will be asked to select the next step, and so on, until the process is completed.
When selecting additional steps after the first one, you can decide if you want the next step applied to the same location as the previous step (this is the default option) or to a new location.
Use cases for applying a next step to a new location might include a big process spanning across multiple teams and projects (for instance a holistic process covering recruiting/onboarding or sales/manufacturing).
As you continue on selecting steps, the right column fills out with a navigation showing the steps selected so far.
You may select steps so long as you have the motivation and information required to decide on a next step.
If you come to a point where you want to await deciding on more steps, you may navigate away from the step selection and into the tasks applied using the navigation in the right colum indicating the steps applied so far.
To resume the step selection process, you can either click the "Select next step" button displayed on the task, or wait for the task to be marked as completed.
When completing a task created from a process step, and provided that there are remaining steps in the process, you will be automatically brought back to the step selector where you can choose the next step from the steps available.
If the step you choose to apply has checklists associated with it, you will be sent to the checklist applier. Here you decide which checklist (if any) you want to apply to the task representing the process step.
To view past applications of a process, navigate to the process in question and click the View button in relation to the application you want to examine.
The application view displays the list of steps applied so far, including their respective application locations.
The process steps of a process can be presented in different views. To change the view, select the desired view from the list of views to the right of the Steps header:
To change the default view of a particular process, edit the process and select the desired default view.
The available views are:
Lists process steps in a branched process map. The color of the process steps match the state of the process step. Double click a process step to view its details.
The process map is best suited for branched processes (meaning processes where a process steps has multiple next steps) as it visualizes the branching.
The process map is the default view, unless a different default view has been explicitly selected for the particular process.
Lists process steps as a list of steps, including step purposes and associated content. To make the expanded view the default view of a particular process, edit the process.
The expanded view is best suited for linear processes (meaning processes where all the process steps only have one next step) as it does not visualize any branching.
Presentations are a way to communicate a topic or collection of ideas to an audience.
Most people are familiar with crafting presentations in software like Powerpoint (PC) or Keynote (Mac). However, there are multiple advantages to creating and managing presentations in a web based platform:
Check out how to Add new information.
A presentation can have one of the following states, indicating what we expect from the expectation at the current stage:
Click the green "View slideshow" button in the upper right corner of the presentation to view the slideshow. The button appears when one or more slides have been added.
The slideshow view is based on the reveal.js presentation framework.
To navigate between slides, you can use one of the following methods:
Hit the "s" key on the keyboard to open speaker view which, among other things, provides you with a timer and the notes associated with each slide.
Hit the "f" key on the keyboard to go into fullscreen hode. Click the "Esc" key to exist fullscreen mode.
When editing a presentation, you can select the theme for the presentation. The theme dictates the fonts, colors and sizes of presentation content.
When selecting a theme, you can choose from a list of default themes, as well as any custom themes that have been added to the organization.
You can add custom presentation themes in order to have presentations look a certain way. The most common use case for a custom theme is to have presentations reflect the brand fonts and colors.
Only admins can manage custom themes.
To create a custom theme, go to Organization > Account > Presentation themes.
Adding a theme consists of either pointing to CSS file hosted on the web containing the CSS rules you would like to include, or embedding the CSS code itself.
Sometimes, simply referring to the main CSS file of you web site might be enough for the presentations to get the look and feel you're looking for. If it's not, you might want to look into the reveal.js documentation describing hw to create a theme.
Use systems to make it appearant where a team is expected to find and store which different types of information, what the states of the various information types are, and to suggest, approve, move into and retire information types as the organization learns more about which types of information are best managed in which systems.
You can view the systems for a team by navigating to the team and selecting "Systems" from the left column navigation.
After adding a system it will appear similar to this:
Each system card includes
When selecting a specific system, the view will look something like this:
Clicking the term for an information type, the view looks something like this:
You can transition an information type between the following states:
To signify that the state of an information type remains valid, or to validate a state selected by another person, select the "Validate current state" option:
Et teams oppgaver fordeles på et eller flere prosjekter.
Dersom et team har kun ett prosjekt blir man videresendt til dette når man navigerer til teamet. Hvis ikke, blir man sendt til listen over prosjekter.
The organizational projects report is accessible by going to Organization > Projects.
The report allows us to:
The report displays all projects across all teams that are either in the planning or in progress stage.
The report is accessible to everyone in the organization, but only include projects owned by the teams to which the user has access.
Teams are sorted alphabetically, whereas the projects within each team are sorted in descending order based on most recent activity.
The right column includes a team-navigation displaying which teams own how many projects in the current view. By clicking on the team name, the page scrolls to the section containing the specific team projects.
It's common for projects to start up, sometimes seemingly out of thin air. Someone has a good idea or someone starts working on something, and all of a sudden, the work has grown into a fully fledged project, occupying its part of the finite work capacity and cognitive resources of the team.
In some cases this might be desirable, whereas in other cases it might divert precious attention and effort away from the primary objectives of the organization.
In order to make it more clear which projects are designed to impact an objective and which aren't, an objective indicator is shown in the project item view. If the indicator is green, the project is associated with one or more objectives. Hover over the indicator to see which objectives the project is designed to impact.
If the indicator is grey, the project has no associated objectives.
In addition to the indicator on each individual project, the right column of the project list (in the context of a team or the entire the organization) includes a progress bar indicating the percentage of projects associated with an objective.
You can associate a project with an objective by going to the objective in question and adding the project as an initiative to the objective.
If the project has a fixed set of tasks to be completed, select this option. This will then produce a warning if you try to add additional tasks to the project.
Select this option if the project is not billable. This information will be used in time log reports in order to indicate that the hours logged to the project are not expected to be billable.
Select this option if the project is not expected to contain its own tasks, but rather references to existing tasks located in other projects.
Use cases for virtual projects are sprint backlogs or other types of work lists expected to represent a list of priorities across the primary team and project location of the tasks.
When a task is presented in a list of tasks at the project top level, the card displaying the individual task includes the following information:
In order to add a new task, click the green plus icon, select "New task" and input the name of the task in the Title field.
If the project is virtual, select the "Add task" option and search for the name or ID of the task you would like to add. You can also add a task directly to a virtual project by ways of the component for Virtual project.
In order to add a checklist, click the green plus icon, select "Apply checklist" and search for the name of the checklist you would like to apply.
You can view the tasks in a project in different views depending on your role and what you're looking to understand.
The default view is the Priority view. To change thew view, click the current view to see a list of available views:
The available views are:
Displays: The top level, remaining (not closed) tasks for a project, sorted by priority.
Use when: You are looking to find your next task.
Displays: All the remaining (not closed) tasks to which you have been assigned.
Use when: You are focused on completing the tasks assigned to you.
Displays: All tasks in the project, sorted by priority, indicating status of completion, by whom and when.
Use when: You are looking to review who completed which tasks when.
Displays: All the remaining (not closed) tasks for which there is a deadline.
Use when: You want to make sure that work is done on time.
Displays: All the completed tasks, sorted by time of completion.
Use when: You want to explore which tasks were recently completed, and in which order.
Visningen for "Endringer" av oppgaver i et prosjekt gjengir hvordan forventningene til tidsbruk for en oppgave har endret seg fra et gitt tidspunkt. Visningen er kun tilgjengelig for prosjekter med et låst omfang.
Dersom oppgaven fortsatt står åpen sammenlignes oppgavens realistiske estimat med det realistiske estimatet på den angitte filtreringsdatoen.
Dersom oppgaven er lukket sammenligns oppgavens faktiske tidsbruk med de realistiske esitmatet på den angitte filtreringsdatoen.
Som standard er filtreringsdatoen satt til forrige bestilling.
Oppgavene er sortert minkende etter størrelsen på estimatendringen.
Klikk på tallet som gjengir størrelsen på estimatendringen for å drille ned på estimatendringer for underlagte oppgaver.
I kontekst av et prosjekt er det mulig å se når og hvor mye tid man er allokert opp.
Dersom det finnes allokeringer registrert så vil det vises ved et bilde av deg selv og med tilhørende allokert tid. Dersom ingen medarbeidere er allokert i et gitt uke så vil det stå Ingen allokeringer.
Tid ført på prosjektet. For mer informasjon, se generell dokumentasjonen for timerapporter.
Prosjektets prestasjon hjelper deg med å holde oversikt over prosjektets evt forventninger til budsjett, omfang og tidsplan.
Svar på spørsmål om avtalens overordnede forventninger. Blå linje indikerer prestasjon innenfor akseptabelt intervall. Rød linje indikerer prestasjon utenfor akseptabelt intervall.
Avtalen viser en graf som gjengir faktisk vs forventet fremdrift og budsjettforbruk på den angitte avtalen.
Grafen gjenspeiler ukentlige, faktiske øyeblikksbilder av fremdriften sammenlignet med en jevn forventet framdrift fra avtalens første til siste dato. Øyeblikkesbildene oppdateres automatisk hver morgen for alle aktive prosjekter.
Et budsjett gir muligheten til å føre tid på og ukesallokere et prosjekt. Dersom man spesifiserer varighet for budsjettet og budsjettet inneholder bestillinger av et konkret antall timer får man også muligheten til å overvåke budsjettforbruket under prestasjon.
Følgende informasjon lagres om et budsjett:
Dersom et budsjett har bestillinger med et definert timeantall, vises hvor mange prosent av budsjettet som er brukt i prosjektnavigasjonen. Dersom budsjettforbruket er over 95% vises en orange varselsindikator. Dersom budsjettforbruket er over 100% vises en rød varselsindikator.
Dersom et budsjett har bestillinger uten et definert timeantall vises hvor mange timer som er ført i prosjektnavigasjonen.
Det gjenspeiles også i prosjektnavigasjonen dersom et prosjekt mangler et aktivt budsjett.
For at det skal være mulig å føre tid mot et prosjekt må prosjektet ha et aktivt budsjett.
For å etablere et aktivt budsjett, opprett et budsjett underlagt prosjektet med en første og siste leveransedato for når det skal være mulig å føre tid på prosjektet.
Budsjettet blir automatisk satt som prosjektets aktive budsjett når dagens dato er mellom første og siste leveransedato.
Du kan se og endre aktivt budsjett ved å redigere prosjektet.
Et budsjett tilføres timer i form av en eller flere bestillinger. Bestillingene gir sporbarhet på hvordan, av hvem og hvor mange timer som er tilført budsjettet gjennom prosjektets forløp.
Gjengir estimatendringer for oppgaver tilhørende prosjektet i valgte datointervall. Standard dato-intervall er fra og med dagen etter prosjektets oppstartsdato, til og med dagens dato.
Estimatendringene er gruppert på
Hvert linje i tabellen gjengir
Klikk på en av tabellenes kolonneoverskrifter for å sortere innholdet i tabellen etter denne kolonnen.
Prosjektets utførende medlemmer. Brukere som legges til vil kunne se prosjektet under Meg > Fremdrift > Prosjekter > Medlem.
Time planning in the platform is centralized around the concept of allocations. An allocation describes how much time someone is expected to spend on something on a given day.
Relevant use cases for allocations are:
Allocations can be associated with:
Unlike a calendar, allocations are not linked to a specific time of day. However, you can Import calendar events as allocations to get a more representative picture of the planned work for a given day.
By keeping allocations current and realistic you can more easily use allocations as your primary TODO-list, while at the same time keeping coworkers up-to-date with how you plan to spend your time.
The best way to think about keeping allocations current is that they should always represent your most up-to-date picture of
Whenever you're done spending time on something, mark the corresponding allocation as completed.
Whenever you realize that you won't have time to do something, move the correspnding allocation do a different date.
Whenever you're interrupted with something you need to spend time on, create a new allocation.
Whenever you realize that something will take less or more time than you originally anticipated, change the duration of the allocation.
Whenever you have planned more work than is available within your plannable time, move things around in order to make each individual workday fit within your plannable time.
The allocation duration indicators takes the plannable time of the user into account. If the allocations exceed the 100% of the plannable time, the indicator turns yellow.
By default, plannable time is set to 7.5 hours / day, but it can be overridden using Personal settings.
Unless you are totally shielded from the outside world (which very few of us are), you should consider lowering your plannable hours pr day.
Most people encounter a significant portion of unplanned work during any given day, so it makes sense to reduce the time available for planned work in order to avoid overplanning.
Best practices for plannable time pr day ranges between 4 to 6 hours. Experiment with what works best for you depending on your roles in the organization and to which extent you're expected to be available for different types of unplanned work.
Each night allocations that are past due will be pushed to the current day. Allocations that have been pushed include a yellow indicator showing for which date the allocation was originally planned.
If the allocation is moved manually, the original date indicator disappears.
Allocations can be created from multiple locations. The most common ones are from the dashboard and from a task.
To view your own allocations, go the focus dashboard.
The colored indicator displayed for each allocation reflects the duration of the allocation.
If the allocation is recurring, a Recurring indicator is displayed.
Allocations imported from a calendar also reflect the starting time of the calendar event.
By default, the focus dashboard displays allocations for the current week. Click the names and dates of the individuals days to expand and collapse the allocations for the given day.
To view the allocations for another time period, use the date picker in the upper right corner to select your desired date interval.
To navigate to the task/project/etc to which the allocation is related, click the desired location in the breadcrumbs trail.
In order to view the allocations of other team members, search for the person in question and navigate to their Focus dashboard.
In order to view all the future allocations of a person, search for the person in question and select "Allocations" from the left menu.
As allocations are completed, you are expected to mark them as such in order to best reflect what's remaining. The best practice for managing allocations is to mark them as your workday progresses.
Here are the optional actions for managing allocations
Select this option when you want to log time in relation to an allocation, but you have not yet finished the allocation. This will trigger the timekeeping form complete with the allocation's related details.
Select this option when you have finished an allocation and want to log time. In the same way as for "Track time", this will trigger the timekeeping form complete with the allocation's related details. When you have tracked time, the allocation will also be marked as completed, and thus disappear from the list.
Select this option when you want to mark the allocation as completed without logging any time.
Select this option when you want to move the allocation to another day.
Select this option when you want to delete the allocation (because it does not represent what you are actually going to work on).
To change the duration of an allocation, click the indicator that reflects the duration of the allocation. This will expose a text field where you can change the duration of the allocation.
To move an allocation to a different day:
If you want to move the allocation to a different day within the displayed time period, you can drag and drop the allocation in the desired day.
The platform integrates with Microsoft Outlook and Google Calendar. The integration means that calendar events can be imported automatically as allocations.
The integration imports the next 100 calendar entries as allocations every 5 minutes, while previously created allocations that no longer have a corresponding calendar entry are deleted.
The duration of the allocation corresponds with the duration of the calendar event.
The integrations have to be authorized in order to be activated.
To authorize the Outlook integration, go to Personal settings and click the "Activate Microsoft Outlook integration" link.
Because of the way the Google integration works, we first have to confirm in our Google integration setup that calendar requests may originate from your platform domain. Contact us with the name of the organization with which would like to use the Google Calendar integration.
If you encounter an error similar to the one below, it is due to the fact that the organizational authorization step has not been completed:
Error 400: redirect_uri_mismatch
The redirect URI in the request, https://[yoursubdomain].wecomplish.no/calendar/oauth2callback, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/442328454474-t9nvbc07rfnnohg44c0hh8vr7g201a5c.apps.googleusercontent.com?project=442328454474
To authorize Google Calendar integration, go to Personal settings and click the "Active Google Calendar integration" link.
By including an ID in the title of the calendar event, the allocation that is created is automatically linked to the relevant content in Wecomplish.
There is support for linking calendar entries to the following types of content:
To associate a calendar event with a task, add a hash symbol (#) followed by the task ID in the title of the calendar event.
For example, if you are going to have an interview in connection with the task with the ID 36964, you can write «Interview John Smith #36964» in the title.
To associate a calendar event with a checklist, use the hash symbol followed by the letter P and the ID of the checklist.
To associate a calendar event with a meeting, use the hash symbol followed by the letter M and the ID of the meeting.
If you have a responsibility that you want to reserve time for at regular intervals you might want to check out recurring allocations.
Recurring allocations allow you to specify how often and on which days an allocation should reoccur.
To administer recurring allocations, select "Recurring" in the left navigation column.
Click creen plus-icon and complete the form fields.
A recurring allocation can be associated with one of the following information types:
If you are selecting a daily frequency, uncheck the weekdays on which you do not want allocations to be created (like the weekend). If you are selecting any other frequency, keep all weekdays checked.
Make sure that the first date of the allocation occurs on one of the selected weekdays.
When you click Save, allocations are automatically created for the next 30 days (or until the last date) based on your selected criteria. Moving forward, an automatic process will create new allocations for the next 30 day period each night.
To edit a recurring allocation, click the red arrow pointing at "Recurring".
When you save your changes the existing allocations created from the recurring allocations are deleted and new ones are created based on the new set of reoccurence criteria.
To delete a recurring allocation, click the three dots in the up-right corner of the allocation card and select Delete.
When you delete a recurring allocation all associated allocations which have not been completed yet are deleted.
Wecomplish gir deg muligheten til på føre tid for å holde oversikt over faktisk vs forventet tidsbruk, og som grunnlag for rapportering og fakturering.
Det totale antallet timer ført for en dag vises til høyre for "Før tid" teksten. Klikk på timeantallet for å se og endre timene som er ført, samt hvor stor andel av tiden som er henholdvis planlagt og belastbar.
Planlagt tid er definert som tid ført i tilknytning til en allokering.
Føring av tid kan utløses fra flere steder:
Hva timeføringen skal knyttes til. Kan være et prosjekt eller en oppgave. Valg av relasjon er obligatorisk.
Dersom du utløser timeføringen i tilknytning til en allokering, via klokke-ikonet på en oppgaveside eller en observasjonsside tilknyttet en oppgave, vil relasjon automatisk fylles ut med den relaterte oppgaven.
Dersom timeføringen er relatert til en oppgave og oppgaven har et estimat, vises oppgavens bullet graph med gjengivelse av hvordan tidsbruk og framdrift vil se ut etter at tiden er ført.
Tidspunktet for når timeføringen startet. Dersom du har ført timer tidligere samme dag foreslås starttidspunktet til slutttidspunktet for for forrige timeføring. Hvis ikke, foreslås tidspunktet 08:30.
Tidspunktet for når timeføringen sluttet. Foreslår tidspunktet hvor timeføringen ble utløst, rundt opp til nærmeste hele kvarter hvis man er mer en 2 minutter inn i det nye kvarteret.
Kun relevant dersom relasjonen for timeføringen er en oppgave. Ved utfylling settes framdrift på oppgaven til den angitte prosenten.
Dersom du utløser timeføringen i tilknytning til en allokering, via klokke-ikonet på en oppgaveside eller en observasjonsside tilknyttet en oppgave, foreslås en fremdrift som beregnes på følgende måte (maks 100):
Eksisterende framdrift + (Forslag til timeføringsvarighet/Oppgavens realistiske estimat*100)
En beskrivelse av hva du har gjort i tidsrommet. Fremfor klassifiseringen av typen arbeid (sjekke mail, behandle observasjoner, lese dokumentasjon, etc), beskrive hva du har jobbet med.
Fyll inn datoen for utført arbeid.
Føringer for type arbeid med påvirkning på lønn (eksempelvis ferie, overtid, etc). Lønnsarten er kollapset som standard og blir automatisk "Ordinær arbeidstid" med mindre du klikker på teksten "Lønnsart" og velger noe annet.
For å endre varigheten på en timeføring, velg Timeforbruk > Timer i venstre kolonne.
Ekspander dagen du ønsker å se timeføringer for, klikk på pilen i tilknytning til timeføringen du ønsker å ende, og velg "Rediger".
Du kan hente ut rapporter over timer ført innenfor et gitt dato-intervall. Standard dato-intervall er inneværende uke.
For å hente ut rapporter naviger til organisasjon, team, person, eller prosjekt og velg timebruk i venstre meny.
Du kan hente ut fire typer rapporter, hvor tidsbruk kan grupperes på forskjellige måter:
Grupperingen for oppgaver viser oppgavene ordnet tilsvarende oppgavens hierarkiske plassering. Gruppene sorteres minkende etter tidsforbruk.
Ved å klikke på pilen som peker til venstre i tilknytning til hver oppgave ekspanderes detaljene om timeføringene.
Klikk på gruppens navn for å gå videre til en rapport om gruppen. Filtreringen på fra og til dato følger med.
Tasks represent something that needs to get done. Tasks can be created in one of the following ways:
To turn the subtask tree of a task into a checklist, click the "Copy to checklist" link. The following information is copied to the checklist:
For å endre en oppgavetittel, gå inn på oppgaven og klikk på tittelen. Gjør endringer, og trykk på V-ikonet, evt bruk tastatursnarveien Cmd + Enter.
En oppgave kan ha en bestiller og en ansvarlig.
Oppgavens bestiller har ingen systemmessig betydning. Denne nyttegjøres kun til å vite hvem man skal kommunisere med for avklaringer rundt arbeidet.
Oppgavens ansvarlig vises i oppgavens listevisning og legges automatisk til som følger av oppgaven. En bruker kan også se alle oppgavene som hen er ansvarlig for på Mine > Oppgaver og evt observasjoner som opprettes automatisk på oppgaven vil tilknyttes ansvarlig for oppgaven.
Dersom man fører tid på en oppgave uten en ansvarlig settes man automatisk som ansvarlig for oppgaven.
Roller vises med navnet til rolleinnehaveren, samt evt telefonnummer og Gravatar dersom disse eksisterer.
En deloppgave er en vanlig oppgave som er underlagt en annen. Deloppgaver gjør det mulig å ordne arbeidet i et hierarki. Du kan bygge et så dypt oppgave-hierarki som du ønsker. Det dypeste nivået vil typisk være det man tenker på som en sjekkliste/huskeliste, dvs ikke "fullstendig" oppgave, men noe som skal gjøres.
Deloppgaver gjengis med den enkelte oppgavens tittel og en avkrysningsboks for å markere oppgaven som utført.
Dersom en deloppgave har en beskrivelse er dette signalisert med en ellipse. Klikk på ellipsen for å se oppgavens beskrivelse (og få mulighet til å markere oppgaven som utført).
Dersom en oppgave har egne, ikke-utførte deloppgaver vises antallet av de åpne deloppgavene i stedet for en avkrysningsboks. I noen kontekster (som visning av prosedyrer) kan du klikke på antallet deloppgaver for å se de underlagte oppgavene.
Dersom en oppgave er blokkert vises et "ingen parkering" ikon istedet for avkrysningsboks/over antallet ikke-utførte deloppgaver.
Dersom en oppgave har en ansvarlig vises vedkommendes avatar til høyre.
Eventuelle utførte deloppgaver skjules som standard, men kan vises ved å trykke på lenken som angir antallet deloppgaver som er utført.
Dersom oppgavelisten er lang (10 eller flere åpne deloppgaver) vises en advarsel med oppfordring om å gruppere deloppgavene.
Klikk på "Legg til prosedyre", søk opp prosedyren du ønsker å legge til, og velg "Tilfør prosedyre".
For å opprette en deloppgave, oppgi oppgavens navn i tekstfeltet "Ny oppgave" og trykk på pluss-ikonet eller Mac: Cmd + Enter/Windows: Ctrl + Enter. Under tekstfeltet vises en forhåndsvisning av deloppgavene som vil bli opprettet.
For å legge til flere oppgaver samtidig, adskill hver oppgave med et linjeskift.
For å legge til et et hierarki av deloppgaver, bruk mellomrom på starten av linjen for å gjengi deloppgavens hierarkiske plassering. Eksempel:
Deloppgave 1
Deloppgave underlagt deloppgave 1
Deloppgave 2
Dersom du oppretter mange oppgaver samtidig (minst 10 linjer med oppgaveinstrukser) vil arbeidet med opprettelsen av oppgaver delegeres til bakgrunnen. Det popper opp et varsel øverst til høyre når dette skjer.
Når opprettelse er delegert til bakgrunnen kan du forsette å navigere rundt på vanlig måte inntil prosessen er ferdig.
Så lenge prosessen pågår vises en melding tilsvarende denne under deloverskriften for Deloppgaver på den relevante oppgaven:
Ved å trykke på "Oppdater status" lastes siden på nytt slik at du kan se oppdatert status.
Når prosessen er ferdig forsvinner meldingen. Unntaket er dersom instruksene krever mer informasjon for å fullføres. Et eksempel på dette er påføring av prosedyre med frister. I dette tilfellet vises i stedet en melding tilsvarende denne.
Ved å trykke på "Tilfør input" får du anledning til å supplere informasjonen som mangler for å fullføre instruksene. Det er kun den som la inn de originale instruksene som har tillatelse til å tilføre input til disse.
Du kan oppgi meta-informasjon om oppgavene som opprettes ved å bruke en meta-syntaks som ser slik ut:
Oppgave
- meta1: Verdi
- meta2: Verdi
Eksempel:
Følgende meta-typer støttes:
Oppgi oppgavens beskrivelse. Rik formatering støttes. Bruk "\n" for å markere linjeskift. Eksempel:
Oppgavens tittel
- desc: Oppgavens beskrivelse.\n\nStøtter rik formatering, som f.eks. [lenker](https://lenke.no/).
Oppgi oppgavens estimat.
Eksempel på et 3-punktsestimat hvor estimatet er optimistisk 1 time, realistisk 2 timer og pessimistisk 4 timer:
Oppgavens tittel
- estimate: 1-2-4
Eksempel på et "sum av underlagte estimater"-estimat:
Oppgavens tittel
- estimate: sum
Når du legger inn eller redigerer et estimat i en prosedyre trenger du ikke "- estimate: ", men kan bare skrive estimatet rett inn i feltet:
1-2-4
Oppgi oppgavens ansvarlig.
Eksempel hvor oppgaveansvaret settes til den som oppretter deloppgaven:
Oppgavens tittel
- assignee: me
Eksempel hvor oppgaveansvaret settes til en bruker med e-postadressen ola@nordmann.no:
Oppgavens tittel
- assignee: ola@nordmann.no
Oppgi blokker for oppgaven.
Eksempel hvor Oppgave 2 er blokkert av Oppgave 1:
Oppgave 1
- id: oppgave1
Oppgave 2
- blocker: oppgave1
Oppgi en midlertidig identifikator for oppgaven. Brukes av andre meta-typer for å referere tilbake til oppgaven (eksempelvis ved oppretting av blokkere). Eksempel:
Oppgave 1
- id: oppgave1
Oppgi prosedyren hvis deloppgaver du ønsker innlemmet. Du kan referere til prosedyren ved hjelp av dens numeriske ID, eller dens identifikator.
Eksempel med bruk av prosedyrens ID (1):
- procedure: 1
Eksempel med bruk av prosedyrens identifikator (kartlegging)
- procedure: kartlegging
Oppgi ID-en til oppgaven i en prosedyre som du ønsker å innlemme. Eksempel med bruk av en oppgave i en prosedyre med ID 1:
- blueprint: 1
Dra og slipp deloppgavene for å sortere de.
Oppgavetitler støtter rik formatering.
For å merke en deloppgave som utført, kryss av i oppgavens avkrysningsboks i listevisning (dersom avkrysningsboksen er synlig). Det er også mulig å merke oppgaven som utført ved å klikke seg inn på oppgaven.
Når en oppgave merkes som utført vil systemet sjekke om foreldreoppgaven har flere åpne deloppgaver. Hvis alle deloppgavene er utført vil du bli spurt om du ønsker å markere også forelderen som utført. Dersom markering av forelderen vil medføre at også besteforelderen ikke har gjenstående deloppgaver vil du samtidig bli spurt om du også ønsker å markere denne som utført, osv.
Dersom oppgaven har blitt opprettet fra en sjekkliste vises dette over oppgavens beskrivelse. Klikk på "Forbedre sjekklisten" for å redigere den delen av sjekklisten som oppgaven er en kopi av, og få muligheten til å forplante endringen til alle åpne oppgaver som baserer seg på denne delen av sjekklisten.
Oppgavebeskrivelsen støtter rik formatering.
For å oppdatere en oppgaves beskrivelse, gå inn på oppgaven, pek på beskrivelsen og trykk på "Rediger beskrivelse" lenken som dukker opp.
Oppgaver støtter Kommentarer.
For å kopiere en oppgave, trykk på "Kopier" lenken. Oppgavens egenskaper som kopieres er:
For å slette en oppgave, trykk på "Slett" knappen nederst til høyre. Du vil bli bedt om å bekrefte slettingen.
Når du sletter en oppgave slettes også alle deloppgaver.
En oppgave kan ikke slettes dersom den selv (eller en av deloppgavene) har tilhørende timeføringer eller observasjoner.
Komponenter er forskjellige typer informasjon som kan knyttes til en oppgave ved behov. Se underlagte artikler for detaljert informasjon om hver enkelt komponent.
For å legge til en ny komponent til en oppgave, trykk på "Legg til" lenken i oppgavens høyre kolonne og velg ønsket komponent.
Komponenter som allerede er lagt til oppgaven vises i oppgavens høyre kolonne under lenken for å legge til nye komponenter.
Enables you to add a task to one or more virtual projects.
Read more about virtual projects here: Create a project.
Lar deg sette en frist for når oppgaven skal være ferdigstilt.
Oppgavens frist er synlig
Fristen gjengis med rødt når den har forfalt.
For å se alle dine egne oppgaver gruppert på frister, trykk på Meg > Oppgaver i navigasjonen.
For å se et prosjekts oppgaver gruppert på frister, trykk på "Frister" i prosjektnavigasjonen:
Hver uke sender systemet e-postvarsler om oppgaver med nært forestående (1 uke frem) og nylig passerte (1 uke tilbake) frister.
Personen som varsles er den som står som ansvarlig for oppgaven, eller den første ansvarlige høyere opp i oppgavehierarkiet dersom oppgaven ikke har en ansvarlig.
Dersom det ikke er satt noen ansvarlig på noen plass i oppgave-hierarket brukes ansvarlig for prosjektet.
Dersom du er spesielt interessert aktiviteten på en oppgave kan du legge deg til som en følger av oppgaven.
Les mer om hvilke aktiviteter følgere Email notifications om på Follow.
For å legge til deg selv som følger, trykk på konvolutt-ikonet.
For å legge til andre som følgere, trykk på pluss-ikonet og velg følgeren du ønsker å legge til.
For å fjerne en følger, trykk på bildet som representerer følgeren.
Lar deg opprette og se eventuelle eksisterende prestasjoner tilknyttet oppgaven.
Listen over allokeringer gjenspeiler ikke-utførte allokeringer i form av:
Dersom oppgaven har utførte allokeringer kan du se disse ved å klikke på "Vis historikk" lenken.
Allokeringer kan flyttes ved å klikke på allokeringsdatoen og velge en ny dato i datovelgeren.
Allokeringer kan slettes ved å peke på allokeringen og trykke på "Slett" lenken som blir synlig.
For å opprette en ny allokering, klikk på pluss-ikonet og følg instruksen for å opprette en allokering.
En blokker synliggjør hva som hindrer videre fremdrift på en oppgave.
Det finnes to typer blokkere:
Velg denne typen når du ønsker å beskrive hva en oppgave avventer. Når du oppgir beskrivelsen vises et søkeresultat med oppgaver og observasjoner som matcher beskrivelsen. Du velger selv om du vil knytte beskrivelsen til en oppgave/observasjon (ved å velge denne), eller ved å oppgi et beskrivelse som fri tekst.
Dersom du knytter beskrivelsen til en oppgave/observasjon vil blokkeren automatisk merkes som løst når den oppgaven/observasjonen som utgjør blokkeren lukkes.
Velg denne typen når du ønsker at noen skal gjennomføre akseptansetesting i et konkret miljø. Den akseptansetester kan velge mellom å akseptere, avslå eller be om endringer.
Identifiser blokkeren du ønsker å slette i høyre kolonne. Dersom blokkeren du ønsker å slette ikke vises, trykk på "Vis historikk".
Pek på blokkeren du vil slette og klikk på "Slett"-lenken som dukker opp.
Når du oppretter et estimat kan du velge en av to typer estimater:
Lar deg oppgi hvor mye tid du optimistisk, realistisk og pessimistisk forventer at gjenstår før oppgaven er ferdig. Tiden allerede ført på oppgaven tillegges estimatet for å gi oppgavens totale estimat. Les mer om trepunktsestimater på Wikipedia.
Ved setting av et nytt estimat beregnes automatisk oppgavens fremdrift ved å se på hvor mye tid som allerede er ført på oppgaven sammenlignet med oppgavens realistiske estimat.
Du kan også oppgi et notat for estimatet, noe som kan være relevant dersom du endrer et eksisterende estimat.
Ved hjelp av funksjonaliteten for Sum av underlagte estimater kan du produsere estimater på milepæler som vil gjøre det enklere for de som er interessert i arbeidet å følge det opp.
Ved bruk av denne funksjonaliteten bør du være oppmerksom på følgende:
Optimistisk, realistisk og pessimistisk estimat kalkuleres basert på gjenstående, manuelle estimater på oppgaver dypere nedover i hierarkiet.
Når estimatet på en deloppgave oppdateres, kalkuleres automatisk foreldre-estimatet på nytt. Hvilken deloppgave som forårsaket estimatendringen vises i tilknytning til foreldre-estimatet.
Kalkuleringen gjøre ved hjelp av beregningsmodellen for prosjektestimat i trepunktsestimering.
Pek på estimatet og trykk på Slett-lenken som dukker opp.
Nye estimater varsles til følgere av oppgaven.
Et estimat representeres i form av en komprimert bullet graph.
De grå bakgrunnsfeltene (i forskjellige nyanser) gjengir hhv optimistisk, realistisk og pessimistisk estimat. De grå bakgrunnsfeltene blir mørkere jo høyere estimatet er.
I eksempelet over er estimatene:
Dersom oppgaven har tidsbruk signaliserer den heltrukne linjen (i eksempelet blå) tid brukt så langt. Dersom tidsbruk er over realistisk forventning blir linjen gul. Dersom tidsbruk er over pessimistisk forventning blir linjen rød.
De svarte markørene gjengir forventet tidsbruk basert på oppgavens fremdrift. I eksempelet over fremdriften 95% som betyr at den første markøren er plassert på 95% av det optimistiske estimatet, den andre markøren på 95% av det realistiske estimatet, og den tredje markøren på 95% av det pessimistiske estimatet.
Ved estimatoverskridelse opprettes automatisk en observasjon av typen "Estimat oppbrukt" (hver natt). Estimatoverskridelse forstås som at tidsbruk overskrider pessimistisk forventet tidsbruk ift framdrift.
Innmelder av observasjonen settes til oppgaveansvarlig *. Det er så oppgaveansvarligs ansvar å sette et nytt estimat og beskrive i notatfeltet hva hen opplever som bakgrunnen for estimatøkningen.
* Dersom oppgaven mangler en ansvarlig settes daglig leder som innmelder.
Framdrift gjenspeiler en vurdering av på hvilket stadie en oppgave befinner seg og prosentvis hvor langt arbeidet har kommet. Nåværende stadie og fremdrift vises som standard, i tillegg til hvor lenge de er siden arbeidet ble påbegynt. Arbeidet vurderes som påbegynt første gang oppgaven ble satt til stadiet implementering eller senere.
Klikk på "Vis historikk " for å se historisk fremdrift.
For å oppdatere fremdrift for en oppgave, klikk på pluss-ikonet i tilknytning til fremdrift. Oppgi oppgavens stadie og prosentvis framdrift, og trykk lagre.
Ved oppdatering av fremdrift på en oppgave kalkuleres og oppdateres automatisk fremdrift på evt foreldreoppgaver.
Det er en forutsetning at oppgaven det føres fremdrift på (i tillegg til oppgavens eventuelle søsken) har estimater for at fremdrift for forelder skal kalkuleres riktig.
Dersom både oppgaven det føres fremdrift på og dens eventuelle søsken mangler estimater, oppdateres ikke fremdrift for forelderoppgaven.
Blokken Tidsbruk gjenspeiler hvor mye tid som er ført mot oppgaven (dersom det er ført noe tid). Klikk på "Vis timerføringer" for å se de konkrete timeføringene.
Tidsbruk vises også i tilknytning til estimatet, evt der estimatet skulle ha vært dersom estimatet mangler. Dersom det er ført over 4 timer på en oppgave og oppgaven mangler estimat gjengis tidsforbruket med rød tekst.
Se dokumentasjonen for estimater for hvordan tidsbruk gjenspeiles i sammenheng med estimater.
Risks represent what we are concerned might happened. The platform exposes the risks of a team in order to:
A risk can be in one of the following states:
Some risks are more severe than others.
In order to better prioritize which risks need to be addressed first, the platform exposes the severity of a risk. The severity is calculated based on the impact and probability of a risk, in accordance with the following matrix:
The risks of a team can be presented in different views. To change the view, select the desired view from the list of views to the right of the header:
The available views are:
Lists risks grouped by risk category, sorted alphabetically. This is the default view.
Lists risks grouped by severity, sorted descending by level of severity.
To view the unmanaged risks across all teams, go to Organization > Dashboard > Unmanaged risk.
The unmanaged risks report is only available to platform admins.
Undersøkelser kan brukes til å proaktivt innhente tilbakemeldinger fra egne team medlemmer eller eksternt som et utgangspunkt for å bli smartere eller jobbe bedre.
Eksempel på bruk av undersøkelser kan være til:
For å opprette en undersøkelse, gå til teamet som skal eie undersøkelsen, velg "Undersøkelser" i navigasjonen og trykk på "Ny undersøkelse".
Når du har opprettet undersøkelsen kan du legge til spørsmål. Spørsmål kan knyttes rett til undersøkelsen, eller grupperes på seksjoner. Seksjoner er nyttig for å gruppere lange undersøkelser, og for å få innsikt i responsen gruppert pr seksjon.
Her er et et eksempel på hvordan rapporten for en besvarelse vises ved gruppere spørsmål på seksjonene "Arbeidet" og "Hvordan jeg blir satt pris på":
For hvert spørsmål som legges til kan du velge hvilken type svaralternativer den som tar undersøkelsen skal kunne velge mellom. Tilgjengelige typer er:
For å ta en undersøkelse, klikk på pilen i tilknytning til undersøkelsen og velg "Ta undersøkelse".
Undersøkelsen viser først spørsmålene som ikke tilhører en seksjon, og deretter spørsmålene som tilhører en seksjon, gruppert på seksjonene.
For å la brukere som ikke har en brukerkonto svare på en undersøkelse, rediger undersøkelsen og kryss av for "Offentlig tilgjengelig". Du kan så kopiere og dele "Ta undersøkelse" lenken med de du ønsker at skal ta undersøkelsen.
Undersøkelser som er offentlig tilgjengelige kan kopieres på tvers av organisasjoner.
Motivasjonen for å kopiere en undersøkelse kan være at du ønsker å vite hvem som har svart, eller å beholde eierskap til og se utviklingen av besvarelsen for din organisasjon over tid.
For å kopiere en undersøkelse, trykk på pilen i tilknytning til undersøkelsen og velg "Kopier".
Du kan også trykke på "Kopier denne undersøkelsen til din organisasjon"-knappen som vises på resultatsiden for undersøkelsen.
To view the details of a response to a survey, navigate to that survey and click the name of the individual who responded to the survey in the "Responses" section in the right column.
To view all responses as a group, click the "Show all" link in the header.
To see all the survey responses of a person, navigate to that person and select Improvement> Responses in the left navigation menu.
To request that someone takes a survey, click the "Request" button in relation to the Responses-section.
This allows you to search for a person or role who you would like to take the survey. An email will be sent to the person you select asking them to respond to the survey. If you select a role, an email is sent to all role holders of that role.
I Wecomplish er observasjoner fundamentet for kontinuerlig forbedring. En observasjon er en beskrivelse av noe som ikke er slik vi ønsker eller forventer.
Funksjonen er bygget på hypotesen om at man vil finne bedre løsninger på problemer man har en god forståelse for.
Observasjoner er et verktøy som sikrer at du utvikler en bedre forståelse for et problem, før du begynner å tenke på løsninger.
Observasjoner kan brukes som et personlig verktøy for å forstå og løse problemer du støter på.
Du kan også involvere andre i observasjonen dersom du trenger hjelp til å forstå problemet bedre, ønsker innspill til løsning, validering av løsning eller andre innspill.
Observasjoners beskrivelse, tiltak og kommentarer støtter Rik formatering.
En observasjon kan ses av alle organisasjonsmedlemmer. Et team-medlem kan se en observasjon dersom vedkommende står som innmelder, ansvarlig eller observasjonen er parkert til et møte hvor medlemmet er møtedeltaker.
Observasjoner støtter Kommentarer.
Du kan oppsøke behandlingsresultatet ved å benytte de dedikerte observasjonssøket.
Noen observasjoner opprettes automatisk basert på automatiserte forventninger i systemet. Observasjoner opprettes automatisk når:
For å endre en observasjonstittel, gå inn på observasjonen og klikk på tittelen. Gjør endringer og bruk tastatursnarveien Cmd + Enter for å lagre.
Observasjonslisten viser observasjoner som venter på deg. Du finner observasjonslisten ved å trykke på knappen "Forbedring" i menyen.
Observasjonslisten grupperer observasjonene på type, og sorterer typene etter en numerisk prioritet gjengitt foran typens tittel.
Observasjoner du har i omløp, gruppert på personen observasjonen avventer.
Observasjoner du har i omløp er definert som observasjoner hvor du har en rolle og hvor observasjonen fortsatt er åpen.
Observasjonene er gruppert pr person observasjonen avventer.
Grupperingen viser først deg selv, og deretter øvrige involverte personer sortert minkende etter antall observasjoner. Observasjoner du har meldt inn som foreløpig ikke har fått en ansvarlig grupperes i en egen "Avventer tildeling" gruppe.
Ved klikk på hver enkelt person vises de observasjonene man har i omløp som avventer den personen, gruppert på observasjonskategori og sortert synkende etter observasjonskategoriens prioritet.
Din egen liste inneholder observasjoner hvor
Observasjoner tilhørende team jeg er medlem av, men det ikke er tilordnet en ansvarlig enda, og hvor observasjonene har en av følgende statuser:
Dersom det finnes observasjoner du er involvert i som avventer deg, eller observasjoner i dine team som ikke har fått en ansvarlig enda, vises som en farget prikk i tilknytning til menypunktet Observasjoner. Fargeindikasjonen betyr følgende:
Bruk Add new information eller tastatursnarveien "o".
* Dersom du synes flere kategorier kan passe, velg kategorien med høyest prioritet (ettersom dette vil påvirke behandlingshastigheten).
Etter at en observasjon er registrert kan den behandles gjennom en arbeidsflyt bestående av forskjellig statuser. Statusen signaliserer hva som forventes gjort med observasjonen og av hvem.
Du kan se nåværende status og hvem eller hva observasjonen avventer under deloverskriften "Arbeidsflyt":
Du kan endre status på en observasjon ved å trykke på den orange prikken over statusen du ønsker å flytte observasjonen til.
Observasjonens status kan også endres som en del av det å legge til en kommentar ved å trykke på den alternative Lagre-knappen. Denne knappen foreslår neste status basert på nåværende status:
En observasjon kan ha en av følgende statuser med tilhørende forventninger til behandling:
Innmelder supplerer med nok informasjon til at observasjonen kan behandles.
Ansvarlig (evt noen på teamet hvis ingen ansvarlig er satt) oppfordres til å ta stilling til observasjonen.
Ansvarlig tar stilling til og tilfører kortsiktig og langsiktig tiltak for observasjonen
Ansvarlig diskuterer observasjonen med egnet samtalepartner.
Ved parkering til diskusjon er det nyttig å supplere med en kommentar som tydeliggjør hvorfor observasjonen er parkert for diskusjon (hva som planlegges diskutert).
Innmelder vurderer om tiltak står til forventningene.
Dersom tiltakene oppleves tilfredsstillende lukkes observasjonen. Hvis ikke, gjenåpnes den med en kommentar som beskriver hva som oppleves manglende.
Observasjonen er ferdig behandlet.
Hvem som innehar hvilke roller i en observasjon er gjengitt øverst i observasjonen. Du kan endre hvem som innehar hvilke roller i observasjonen ved å begynne å søke etter en persons navn i rollefeltet og velge personen som matcher søket.
Innmelder for en observasjon er den som har gjort seg observasjonen og har en interesse i eventuelle tiltak som identifiseres.
Ansvarlig for en observasjon er den man ønsker skal ta ta stilling til tiltak. Om du ikke setter en ansvarlig vil observasjonen bli synlig for alle som tilhører teamet observasjonen er opprettet i slik at en person med kapasitet og rett kompetanse kan ta ansvar for observasjonen.
Et tiltak er noe noen har gjort eller planlegger å gjøre for å utbedre situasjonen på kort sikt (kortsiktig tiltak) eller unngå at situasjonen gjentar seg (langsiktig tiltak).
Dersom du velger en forelder opprettes automatisk en oppgave med samme navn som tiltaksbeskrivelsen, oppgaven lenkes til observasjonen og observasjonstiltaket lenkes til oppgaven.
Dersom du ønsker å kvalitetssikre tiltaket for en observasjon på et senere tidspunkt kan du sette en gjenåpne dato på observasjonen. Observasjonen vil da automatisk bli satt tilbake til steget "Kartlegges" på den valgte datoen, og få en kommentar med teksten "Automatisk gjenåpnet".
Du setter en gjenåpne-dato ved å redigere observasjonen og oppgi en dato i feltet "Gjenåpne".
Observasjoner med gjenåpningsdato satt viser gjenåpningsdatoen i tilknytning til Arbeidsflyt for observasjoner.
Møter er et sted hvor observasjoner kan parkeres for diskusjon.
Du kan opprettet møter på forskjellige måter:
Det er kun ansatte som kan slette møter.
Agendaen vises når du navigerer til et møte via møtelisten for teamet eller søk. Det finnes også en print-tilpasset versjon av agendaen med en innholdsfortegnelse i toppen.
Øverst vises en liste over personer som har observasjoner parkert til agendaen med tilhørende antall observasjoner de har registrert. Klikk på en av personene for å filtrere agendaen til å kun inneholde observasjoner fra denne innmelderen.
Ansatte kan se alle møter. Kunder kan se møter hvor de er møtedeltakere.
Et team-medlem må være møtedeltaker for å kunne se et møte og observasjonene parkert til dette.
Trykk på det grå krysset til høyre for møtedeltakerens navn for å fjerne deltakeren fra møtet.
Understanding the market in which one operates is a crucial part of success of any organization.
The information types and functionality organized under the Market category seeks to help identify and share these types of insights.
Managing market insight has multiple benefits:
In short, managing market insights helps make the go-to-market process a more predictable, transparent and continously improved process.
A study showed that once an organization agrees on
...the organization is is five-times more likely to create a product or service that wins in the marketplace.
Market insight is relevant across multiple departments of a traditional business, including:
In addition to describing the organizations publicly facing solutions, the market functionality can also be used to describe profiles and solutions that are served internally within the organization (internal market) to help gain a better understanding of how each team is set up to support other teams.
The information types are inspired by well-established methodologies like the Value Proposition Canvas and Outcome Driven Innovation.
Here's an overview of how the main market information types are conceptually associated to oneanother.
Note that profiles and solutions are not associated directly, but rather through associations between the outcomes associated with a profile and the benefits associated with a solution. This design aims to reduce the risk of assuming which solutions fit which profiles.
A hypothesis is something we belive might be true, but which we have not been able to prove or disprove (yet).
Although hypotheses are a very common tool in scientific work, they have yet to become popular and operationalized in non-academic circles. The platform aims to change that.
There are a multitude of benefits associated with adopting a hypothetical mindset within a team or an organization, including:
Hypothesis are especially relevant for innovative, growing and high performing teams continually on the lookout for a better understanding of the world around them and a more optimal way of doing things.
This includes, but is not limited to:
If you do not have any hypothesis to test, it's useful to ask yourself if you are doing sufficient innovation within your domain.
Hypotheses can be organized into different groups. In a startup, the hypotheses can most commonly be placed into one or more of the following four categories:
A hypothesis can have one of the following states:
The Organizational hypotheses report provides an overview of the hypotheses that are currently a priority for the organization.
The report displays the hypotheses that are either on the Considering or Experimenting stage, across all teams.
Profiles describe the types of people we are interested in helping.
Motivations for describing a profile includes
If your organization has existed for some time, you have probably already seen a pattern in the people that you are helping, and you'll be able to deduce a set of profiles from that insight. You might also have had specific thoughts or discussions with regards to which types of people you want to help, and which types have proven not to be worth the effort.
If you, on the other hand, are just starting out, these patterns and discussions may not have emerged yet.
In this case, before identifying a profile, aim to have met with at least two people with a similar/overlapping set of desired outcomes before identifying a group of people as a profile. If you don't, you might incorrectly assume that one person cares about the same outcomes as someone else based on relatively superficial characteristics like their role.
The intuition when naming a profile (especially if you're delivering to the B2B market) is to use job titles. In a profile context however, this doesn't give us much to work with as people seemingly in the same role aren't neccessarily focused on the same outcomes.
For better profile naming scheme, try combining these three factors in the profile name:
Here are some examples
Creating more specific profiles helps us narrow down the outcomes and more easily personify and identify with the profile.
Be wary of creating too specific profiles, as there won't be enough people matching it, and as a result it will make less sense to invest time and effort into building out and targeting the profile.
Since creating a profile takes time, it does not make sense to create profiles for anyone and everyone you might encounter or think of.
We want to focus on describing profiles where the benefits of sharing the profile insight with other team members outweights the cost of organizing and absorbing the insight.
When considering adding a profile, check to see if it matches the following criteria:
The intuition when describing profiles is to focus on the people outside our organization that we're looking to help (external profiles). However, most teams within an organization also have a role in helping people inside the organization (internal profiles).
Here's an example:
A product team within a tech company might identify their external profiles as different types of users of their product. However, the product team also needs to satisfy internal profiles, like:
In order to get a balanced view of priorities and stakeholders, make sure to consider both external and internal profiles when deciding which profiles are worth describing.
In order to better understand the needs of the people associated with a profile, the profile makes room for describing the desired outcomes of the people who identify with a profile.
The desired outcomes are grouped into three separate types:
Desired outcomes are reusable across profiles. This means that when you add a new job, gain or pain, the system searches for desired outcomes already defined on other profiles.
A profile can have one of the following states:
Propositions help us systematically improve our understanding of what profiles in our market care about.
The purpose of propositions is to
To get started, you first need to create create a proposition. You can do this by going to the Team > Propositions, and selecting "New proposition".
A proposition is simply a collection of which profiles you think the people you plan to proposition identify with, and the preferred language of the people you plan to propositions.
In most cases you'll probably want to stick with one profile, but at an early stage where you have little to no information about your target market, you might want to experiment with several profiles in order to see which labeling the interviewees most identify with.
A proposition also allows you to select a proposer, meaning the person who is responsible for communicating the proposition to others. Usually, this will be yourself, unless you are constructing propositions on the behalf of others, i.e. the members of your sales or marketing team.
Setting a proposer helps keep track of which individuals are working on which propositions, and better understand the activity and data gathered by each proposer.
If you are interviewing people digitally (meaning you are sending them the consideration survey to reply for themselves), the proposer will also appear as the sender of chat-like messages in the consideration wizard, and will receive an email when someone signals their interest in a proposition.
If you have identified individuals who you want to consider your proposition, you can add these as a new consideration, giving their name and email address. This will produce a unique consideration wizard link in which the person will be greeted by name and you can see to which extent this particulare individual expresses interes in the proposition.
If you have not sourced particular suspects for a proposition, or you want to make available a public link (for instance on a web site) where anyone can provide their consideration, use the generic consideration wizard link.
Considerations are a way to collect feedback on the profiles and outcomes of a proposition.
The feedback collection is done through the consideration wizard.
The consideration wizard gives us the ability to collect feedback on which profiles and outcomes people actually identify with and care about.
The consideration wizard can be used digitally by the interviewee themselves (if you send them a link), or by a researcher calling to survey the interviewee.
Here's a screenshot from a step in the consideration wizard process:
The wizard consists of the following steps:
The interviewee selects which profiles they identify with.
The interviewee rates how important the outcomes associated with the profiles they've identified with are to them.
If they care at all about an outcome (meaning it has somewhat importance or higher), they are also asked to grade their current satisfaction with their ability to acheive the desired outcome.
The interviewee receives a summary of the outcomes they care about and signals their interest in being contacted again in the future.
The input provided by users when considering a proposition is available in different contexts. To learn more, check out Opportunity score.
Opportunity score is a tool that helps to
Opportunity score is the main metric in the Opportunity-Driven Innovation framework created by Anthony W. Ulwick, which aims at “making innovation predictable”.
The score is the result of an analysis of the gap between the importance that customers assign to the expected outcomes of a job-to-be-done, and how satisfied they are with their current solutions.
The formula looks like this:
Opportunity score = Importance + (Importance - Satisfaction)
Opportunity score is calculated based on the data collected by the Consideration feature.
As such, you have to be actively collecting input via the Consideration wizard in order for the opportunity score to appear in relation to the relevant outcomes and profiles.
Opportunity score is exposed in the platform in the following ways:
When listing the relevant outcomese of a consideration, each outcome contains a label signifying how relevant the outcome is to the interviewee. The opportunity score is displayed within the label.
These are the relevancy labels used depending on the opportunity score:
When viewing a profile, the outcomes that have been evaluated (as a part of consideration) include the opportunity score.
Here the opportunity score is presented as a percentage of what is possible in order to better compare the opportunity of different outcomes.
To view the outcomes in descending order of opportunity, select the opportunity view:
This helps you identify which outcomes have better resonnance (opportunity candidates) and which are considered less relevant and should be retired from the profile once you have sufficient confidence in the data.
When viewing a list of profiles, if the profile has one or more considerations, the total opportunity score of the profile is displayed on the profile card:
This helps you identify which profiles have better resonnance (opportunity candidates) and which are considered less relevant and should be rejected once you have sufficient confidence in the data.
Solutions are the products and/or services we are offering to help the profiles we are serving.
Here's an example of what a list of solutions might look like:
The benefits of a solution are broken down in to two types:
A singular benefit can be associated with multiple profile outcomes, tying the solutions offered to the outcomes people care about.
A solution can embed other solutions. Relevant use cases for this might be a software product consisting of multiple modules that are themselves considered separate solutions, or when building a custom solution for a client consisting combining several pre-existing solutions.
A solution can have one of the following states:
In order to be successful, we need to get people to make the switch from whatever they are doing or using today, and over to us.
The more deeply we understand the alternative ways in which our market is getting the job done, the better equipped we will be at building better solutions and communicating the benefits of making the switch.
Ensuring that people are actually using alternatives also helps us to validate the fact that the problem is seen as worth solving by the market, and to refine our understanding of the problem and how it is understood by the people we want to help.
To facilitate this type of insight, the platform supports managing Alternatives as an information type.
Alternatives helps us share insight across the organization into how the market is currently solving the problem, and the advantages and disadvantages of those alternatives.
Alternatives might consist of neatly packaged products and services provided by organizations we consider to be our competitors, but they could just as well be Excel spreadsheets, templates, recurring meetings or other manual processes constructed to help get the job done.
Understanding the alternatives to our offering is valuable, not only to the people working inside the organization, but also to those who are considering investing in us. Being able to demonstrate a deep understanding of alternatives is highly valued by and reassuring to potential investors.
An activity is an action taken in the platform. Activities are automatically created when a logged in user performs one of the following actions:
In the context of the organization, a team and a persons, you can find a visualization of the activity.
The activities are grouped into three categories:
The charts display the activity count for the last 5 weeks. Point to the chart to see the exact week number and activity count for a given week.
On the organization and team dashboard, the charts include a list of activity contributors in the upper, right corner, sorted in descending order by activity count. Point to a user to see the exact activity count for the entire period.
The purpose of grouping activity by executing, documenting and improving is to better expose how a team or a persons contributions is divided among short-term and long-term work. This can then be used as the basis for reflection and discussion during a team status meeting or a performance review.
The general expectation is that, once a team or person matures, activity is expected to shift more from the left (more operational activity) to the right (more strategic activity).
It's helpful to understand and be sensitive to different peopls proclivities towards either execution or facilitation (documenting and improving) when having this discussion, all the while calibrating expectations towards the relevant responsibilties and seniority/maturity.
You can easily discover to which extent, where and by whom there is activity within the platform.
Here are some of the ways in which to monitor activity:
Click the "Organization" navigation item in the top menu and scroll down to the Activity section in the left column.
Here you will find the following reports:
In addition to these purpose-built activity reports, you also have the "Recent activity" report in the top of the left column summarizing activity within the current week.
Navigate to a specific team to see:
Navigate to a specific project to see:
Navigate to Organization > People or Focus > Priorities My team to see the activity indicator for each individual person, or all the people within your team.
The activity indicator has the following different colors:
The amount of upward pointing markeds depend on the activity count:
Navigate to a specific person's profile page to see:
To get the best and most out of our people, we need to make sure that they remain focused. This involves
Use the focus report to quickly get an overview of the focus of individuals within the organization. To view the report, go to Organization > Reports > Focus. The Focus report is only available to Platform admins.
Here's an example of what the Focus report might look like:
For each individual, the reports displays:
If the number is higher than 10, it appears in red. If the number is higher than 5, it appears in yellow, indicating that the person might be stretched too thin.
In the right hand column, there are graphs indicating the percentage of individuals who are focused on at least one project, objective and expectation respectively.
Rapporten gjengir forpliktet (i utgangspunktet belastbare prosjekter som er underveis) kapasitet vs tilgjengelig belastbar kapasitet fram til valgte uke. Som standard vises 26 uker (et halvt år) frem i tid.
Den forpliktede kapasiteten består av resterende timer (oppdatert hver natt) forventet levert på budsjetter med et dedikert timeantall.
I tillegg vises, i tilknytning til forpliktet kapasitet, den planlagte leveransen frem i tid (i form av ukesallokeringer).
Budsjettene sorteres fra størst avvik mellom resterende budsjett og planlagt tid, til minst.
Klikk på "Vis allokeringer" i tilknytning til det enkelte budsjett for å se hvilke ukesallokeringer som er planlagt for budsjettet.
For å også inkludere ikke-belastbare prosjekter, kryss av for "Inkluder ikke-belastbare prosjekter".
For å også inkludere prosjekter som avventer, kryss av for "Inkluder prosjekter som avventer".
NB. For at grafen skal vises riktig må det være lagt inn belastbar kapasitet på minst én ansatt i organisasjonen.
Viser belastbare ressurser og deres planlagte kapasitet i form av belastbare timer for et gitt datointervall.
Pek på bullet graphen for å se belastbar kapasitet for den enkelte.
Rapporten for forpliktelser viser prosjekter med låste, aktive budsjetter, og forventningen til hvor mye tid disse på allokeres opp pr uke for å levere budsjettet innen avtalens utløp.
Forpliktelsene er sortert etter antall dager til forfall fra lavest til høyest. Forpliktelsen er grålagt hvis det ikke finnes noen oppgaver som kan utføres, prosjektet er satt til avventer, eller prosjektet ikke har startet enda.
For hver forpliktelse vises følgende informasjon:
Første kolonne gjengir anbefaling til allokering. Dersom forpliktelsen allerede oppleves ivaretatt, vises ingenting.
Dersom faktisk allokering avviker med mer enn 30% av "bør allokere", vises en avkrysningboks med en blå eller rød bakgrunnsfarge. Blå gjengir > 30% overallokering. Rød gjengir > 30% underallokering.
Status forteller hvor a jour vi er med tidsbruk pr d.d. sett oppimot forventet tidsbruk pr d.d. Eksempelvis viser en status på -10:00 at vi har levert 10 timer færre enn vi hadde forventet (med et jevnt tempo) på dette tidspunktet.
Bør allokere gjenspeiler hvor mye tid som må allokeres pr uke for å komme i mål med prosjektet innen deadline. Forventningen beregnes med utgangspunkt i hvor mye av budsjettet og hvor mange arbeidsdager som gjenstår å levere.
Kolonnen pr medarbeider gjengir antall timer vedkommende er allokert opp på forpliktelsen. Lyseblå bakgrunn gjengir at vedkommende inngår i teamet for den aktuelle forpliktelsen.
Gjengir antall registrerte observasjoner (herav antallet observasjoner automatisk registrert) pr person eller team for rapportperioden.
Under Rapporter > Oppgaver kan du søke etter alle oppgaver på tvers av organisasjonen.
I tillegg til et fritekstsøk støtter søket filtrering på:
Rapport som gjengir antall registrerte prestasjoner pr innmelder for rapportperioden.
Viser de aktive budsjettene som har timer ført. Budsjettene er sortert minkende etter antall timer ført.
For budsjetter hvor siste leveransedato har passert vises denne datoen i rødt.
En spesifikasjon presenterer en oppgave, et prosjekt eller en prosedyre med tilhørende deloppgaver og estimater i et utskriftsvennlig format. Spesifikasjonen formål er å gi arbeidets interessenter et overblikk over det totale omfanget av arbeidet, typisk som grunnlag for en bestilling eller å kvalitetssikre forståelsen av arbeidet.
For å vise spesifikasjonen for en oppgave, klikk på lenken "Spesifikasjon" nederst på oppgavesiden.
For å vise en spesifikasjon for et prosjekt, klikk på pilen i tilknytning til prosjekttittelen, og deretter på lenken "Spesifikasjon".
For å vise en spesifikasjon for en prosedyre, klikk på pilen i tilknytning til prosedyrens tittel, og deretter på lenken "Spesifikasjon".
Spesifikasjonen er delt inn i to hoveddeler - estimater og beskrivelse av arbeidet.
Presenterer estimatet for spesifikasjonen totalt, samt estimater for oppgavene direkte underlagt. Oppgavenes navn i estimat-tabellen lenker til oppgavens beskrivelse.
Estimattabellen vises kun dersom selve oppgaven også har et estimat (i tillegg til underlagte oppgaver).
Presenterer oppgavetitler og beskrivelser for hele oppgavehierarkiet. Vekten på overskriften gjenspeiler dybden i oppgavehierarkiet. Oppgavetitler foranstiles med kapittelnummerering tilsvarende oppgavens rekkefølge og dybde. Oppgavetitlene lenker til den fulle oppgaven.
Users have three different access levels. You can identify the current access level of a given user in the right column of their profile page:
An administrator is someone who is expected to manage the organization within the platform.
The administrator can use all functionality and view all content stored in the organization.
The only exception is tasks not explicitly associated with a team. These are only accessible by the creator and assignee. The tasks are stille available in searches and lists.
Admins can be managed by going to Organization > People > Administrators. You have to be an administrator in order to grant other people administrator priveligies.
A team member is someone who is expected to maintain team insight.
Team members can view and edit the information of all open teams, and any private teams they have been granted explicit access to.
They can also see the names of any private teams and who is granted access to those teams, but they can not view the contents of those teams unless they have been explicitly granted access themselves.
A collaborator is someone who collaborates with, has input to or is interested in the work carried out by the team. Typical use cases include representatives from clients, vendors or partners.
A collaborator can view, search and comment on all of the team's content, assign and perform tasks, and create observations and achievements.
Teams have two different access levels. You can identify private teams by the padlock displayed next to the team name.
This is the default state when creating a team. Private teams are accessible by admins and users granted explicit access to the team.
When creating or editing a team, you can choose to make the team open.
An open team will have its contents viewable and searchable to any user in the organization.
To make an existing team open, navigate to said team, click the icon in the top right corner, and select "Edit". Then, check off the "Open team" checkbox.
When a user is no longer expected to have access to the organization, navigate to the profile page of said user, click the ellipsis icon in the top, right corner and select "Retire from the organization".
Retiring a user will also remove their:
After retiring the user from the organization, that user will no longer be able to log in, but the content they have produced will still be available.
If you need to reactivate a retired user, navigate to the retired user, click the ellipsis icon in the top, right corner and select "Reactivate in organization".
Make sure to recreate any of the information that was removed when retiring the user.
For å gjøre det enklere å evaluere plattformen uten å eksponere og manipulere produksjonsdata for en reell organisasjon er det mulig å nyttegjøre en generell demo konto eller opprette en egen konto.
Se hvordan du oppretter en organisasjon.
Demo kontoen er foreløpig kun tilgjengelig i utviklingsmiljøet ved å sette opp miljøet til å svare på julenissen.* som subdomene.
Utover data som brukere av demo kontoen selv legger til/fjerner kan du forvente å finne et sett med grunndata avhengig av hvilket datasett som er påført demo kontoen.
Datasettene som er tilgjengelig er definert som en del av kodebasen på Alice fixtures formatet.
Dersom du ønsker et rent datasett (renske demoen for data tilført/fjernet manuelt) kan du resette demoen. Resetting av demoen innebærer effektivt at hele demokontoen slettes og opprettes på nytt med demoens datasett.
For å resette, kjør følgende kommandoer:
php bin/console tenant:delete julenissen
php bin/console hautelook:fixtures:load --append