Skip to content

Commit 49ded24

Browse files
author
Jérémie Grodziski
committed
Fix typo
1 parent e5b41a9 commit 49ded24

File tree

2 files changed

+12
-1
lines changed

2 files changed

+12
-1
lines changed

contributors-email-address.txt

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
fle@youragileway.com
2+
jerome.regnier@socgen.com
3+
yoni.boukhobza@socgen.com
4+
celia.carceller-kemiche@pole-emploi.fr
5+
nicolas.chevalier@gluendo.com
6+
francois.bivaud@pole-emploi.fr
7+
olivier.jauze@michelin.com
8+
thierry.fraudet@michelin.com
9+
gael.herent@thalesgroup.com
10+
olivier.trantoul@thalesgroup.com
11+
romain.chapon@michelin.com

landing/content/pages/home.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ features:
3434
*What are the major issues facing your enterprise?* Engineers and architects are proficient at solving problems, they are often less skilled at challenging the way problems are stated. Spending time solving the wrong problem wastes the enterprise's time and resources. Therefore, Continuous Architecture recommends to pay attention to the way problems are framed because it largely influences solutions. Reframing a problem can sometimes help you find radically different and more effective solutions. The discovery of a problem begins with an acute sense of observation that leads you to ask the right questions. Reframing also requires the open minded attitude that can help you think out of the box.
3535
icon: assets/imgs/magnifier-icon.svg
3636
url: /docs/problem-discovery/problem-discovery.html
37-
left:
37+
left :
3838
title: "Framework"
3939
text: |-
4040
The tools and kits we have created can be used in isolation or they can work together to help the enterprise change to be more successful. In a **V**olatile, **U**ncertain, **C**omplex or **A**mbiguous world, it is important to bring structure while enabling business and operational agility. The Continuous Architecture Framework (CAF) combines intentional architecture and emergent design to help autonomous teams align around a common purpose and a set of shared Objectives and Key Results (OKRs) while preserving agile teams' autonomy. Team autonomy is a pre-requisite to speed because it reduces coordination activities that slow down teams. On the other hand, when autonomous teams are mis-aligned it increases the risk of delivering poor client and employee experience due to ineffective coordination.

0 commit comments

Comments
 (0)